Result for 767406C6263CA5BCF64667551CE3093177D26CFC

Query result

Key Value
FileName./usr/share/maven-metadata/httpcomponents-core.xml
FileSize3606
MD5E48A28D26DEF67D19BCEE671E6114CA2
SHA-1767406C6263CA5BCF64667551CE3093177D26CFC
SHA-2568DD47276C82F0B81B925E2202E2D5BE1FD083C8E16A9FC10A5F29CBBD92BC98A
SSDEEP48:cmAAhtZNBaoYatyscCatytDsCatR/YCSINyI7hatRqZCSINyI7hdtyYtydty1tRj:LAAhLYaACaWsCaMCSIFamZCSIFdX6eRV
TLSHT19A71F3F0A9FD907172A049C09E32FA53FFD094B7E891128DB0DF41994F8ACC982B305A
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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
MD57B79270DFC02F7F7ED2A4EA260017384
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.fc24
PackageVersion4.4.4
SHA-1395C678A3580233A779BDAFB98C51238992ADC71
SHA-2561866D4EA6DE080FE040DC7F1F79335523429595E05217547699C61BB1D14114C
Key Value
MD5183D3888BA13C60DD7E30284E7AFCC20
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.fc24
PackageVersion4.4.4
SHA-180F3BC80852E79B5B38A13E52365D9CAB0B846F2
SHA-25600356159C70ABC1557F2A1595F1682AF1A983D96A1A45DC4C804AE10AA4B7B6C