Result for 44F649F682A8F4CAAFAD01608B28C79E84FE9932

Query result

Key Value
FileName./usr/share/doc/httpcomponents-core-4.2.2/RELEASE_NOTES.txt
FileSize44245
MD5ADAF8302F1B056814BC29651CB3E9A0C
SHA-144F649F682A8F4CAAFAD01608B28C79E84FE9932
SHA-256A736D5BEECA1C02F62EB3082D4E02101015710D80DFC6E017E2309783431676A
SSDEEP768:sPj5DuiPTuh12Z0edjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKg19Z+:8PaT2VIxwuCfZWW6CfSzs8
TLSHT15D1351313E4933350E13D4D7DBC39541EBFDA89CE7A564F2558CC41C229A8A882BF6D8
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5C4EE188ECCBFDAD57C67752F66D138E1
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
PackageRelease1.fc18
PackageVersion4.2.2
SHA-19A3EEF50FE776947182B8CD0C4E395C815B93DFF
SHA-256C6CA6DB73284CD3F22761A92BB07BA02BF4FFFD3575AA7F7819604E0B4F8CD06
Key Value
MD5E01B0E6F8A6A24C9FFE3F90D3D148D51
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
PackageRelease1.fc18
PackageVersion4.2.2
SHA-1F2E344A93B55F56B5247D988A72A7893A0A4F58B
SHA-256499748CB0E90E7F5B77810552E36BA80355C82F298442AC7BE2A8CE26EB2FAD9
Key Value
MD536FE84BFCB796AD3D4C2292CA97522FE
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
PackageRelease1.fc18
PackageVersion4.2.2
SHA-10FCCE1CDDFB38E9FE3D9B2578C4F04CE43D27C90
SHA-256A59CAC5445F7D039373BC606F07032E043C4EBD3F3376909DE49FB1FF984444D