Key | Value |
---|---|
FileName | ./usr/share/maven-effective-poms/JPP.httpcomponents-httpcore.pom |
FileSize | 41388 |
MD5 | B3D10A6E8057C0C9BA4D3E2F9D78EDD8 |
SHA-1 | 0BDB82BBAF607D58ECAE6B507C8EAF681A73FF62 |
SHA-256 | 20CAB1E325281B364190724D5DA573D488851FDC90B6B4052EA5E9C73C1A9266 |
SSDEEP | 768:OA0bFGL8hYjzU9rwXz+oD9MrXO/Dj9RnZFc9mZFc90ZFc9nJVs9h2hXq/:O1bozU9rwXz+oD9nD3ZFc9mZFc90ZFcw |
TLSH | T1D803CFF19CFC59F2215609C65B2169C2BFFAC2EBD8858008F5DD5B056F8DDCE42A3A12 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | ED4FE72CDEAC93FB84844F3ED8BD8F87 |
PackageArch | noarch |
PackageDescription | HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner. |
PackageMaintainer | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 5.fc20 |
PackageVersion | 4.2.4 |
SHA-1 | E928D9263910169485F92829E8F1BF78322E3211 |
SHA-256 | 9A0C6A9657F7C88B5737D96D100562B2217DF442F9E36E5F2FA07DDED8E02C61 |
Key | Value |
---|---|
MD5 | C178CDCFC889F9859297B1F77C8B2CEE |
PackageArch | noarch |
PackageDescription | HttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner. |
PackageMaintainer | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 5.fc20 |
PackageVersion | 4.2.4 |
SHA-1 | CA3CE3A386D272818B894F696580831ACFFE67A6 |
SHA-256 | A562688ECE9B6D355711C7F312BE05AA141D33106BFD86CB14C4616240C6F94A |