Result for 4D50CE4EC2EE14BC117B40F9C80E418B441B18A4

Query result

Key Value
FileName./usr/share/doc/httpcomponents-core/RELEASE_NOTES.txt
FileSize75357
MD583082CCB999A4589471F2AF9910C0D55
SHA-14D50CE4EC2EE14BC117B40F9C80E418B441B18A4
SHA-25603AEA8C692CC0D52C85D0EFFBC67A97A544AB2C0299026CB85291EE6E95058EF
SSDEEP768:fsJ+jRWuycsRccdb7fhxrInd2X0kdjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKb:k8PUxsd2tIxwuCfZWW6CfSzs8
TLSHT1C67394317E9D33350E13D5E7DBC35501EBF9A89CD7AA54F25A4CD00C219A8A882BF6D8
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
MD58E022A42A9EBFA630FE9CEE06074EC95
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.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-18311940DAA3355A7A629D63997F53BAC94733A77
SHA-256B852E73CB8344B8956D62823E0EE2A2B3D01ECE75058F9B829B640C1F231438A
Key Value
MD58448844877E55454CB0D565CF066F125
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.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-13324424E045A841626772C9E1A756FCF2B3E0038
SHA-25654126A46046CE827DCBF57429DD76F202ABFFFBF3BC7CB8C04011EF40D1CC41D