Result for BF837D1AE808E9AFBE04D52A81DFDC1267997B08

Query result

Key Value
FileName./usr/share/doc/httpcomponents-core-4.1.4/README.txt
FileSize2281
MD534B36FFA34A96D05913671E52A0D7F4C
SHA-1BF837D1AE808E9AFBE04D52A81DFDC1267997B08
SHA-25631891B412AB0563913018E5FCABDEC5800ACC27B16479B8380A2BFBE24E7D679
SSDEEP48:B79KcqAHf9RqZyYiHED6aXNLQCEg9ek9XQe:B79KMHf9Rq3iHseCEg979L
TLSHT19D416117BD28A72111E2C3A1A7B69085FBBF6798F285112CEC1242B05314FE0C67F1A4
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
MD5AC6DB1CC2ADBB3EFACC983D9155A78FA
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.fc17
PackageVersion4.1.4
SHA-1FDD205DA20779D880C3F00306F57F70F8981CBFE
SHA-2563F0C4AF69DEF0AD646599209CB16E3BE3CFDCBDF7DF2C7D7D082F824301770F2
Key Value
MD592007BB51AD9DC2E72DC1B5AD6EDC67F
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
PackageRelease3.fc15
PackageVersion4.1
SHA-1E5532980A90CF042F48131FDDD1B28DCEBBFF892
SHA-256BFDC82C9530CA0AA41706B503FDF9EAA3647D1D73294C26BA36998329FB501E0
Key Value
MD5F704249C937C9444631438292BC0B93E
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.fc16.1
PackageVersion4.1.3
SHA-10D1B1429DE7AFF73E8D26F66F721531FF35134A9
SHA-256F6B3AEC4C7F2ACBEBEBB99E11B474C08DB290B5F9F38A92F938CBCABA955C414
Key Value
MD5A059DB16DA3E6545CD639B972CBDD47B
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.fc17
PackageVersion4.1.4
SHA-1958A95DD8D2C988CC2D53DA7E58A2D4F17A2AA68
SHA-25698849B8B77628CC9C1EA47C4B1E9B96B3EE087BE09AD2F0D8D5588C1AF5C4D36
Key Value
MD5DD1801E6FEE2C9F9840DEDC5CCA1A34C
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.fc16.1
PackageVersion4.1.3
SHA-1599B45F567E95292B4226E8E9D23674BF683C84C
SHA-256E29910A6F51C3D5922709017332F73570E30E27232911CCD8A7BE95E3DB22306
Key Value
MD5E593855A18CD7441BE07D7578334A395
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
PackageRelease3.fc15
PackageVersion4.1
SHA-11874EE688DCB983DF7337C1B847503A993CC0BBD
SHA-2569501384227C3DB9122A8C6470E4E99F83E01CCB96578F4827977A282CA733742
Key Value
MD5E9DC76DDFDEFEAE10ADCCCD37AE7A576
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.fc17
PackageVersion4.1.4
SHA-1FCA5089A3BEF68BB91F69A73ED8542829DEACD55
SHA-256F050013D9F325299FC6B8A14C2C65AF34E1EF4336FDF5C962EC1AFC1AB27678D
Key Value
MD5C2FBE23041C1F6365CDEB11F65BD5F47
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
PackageRelease3.fc15
PackageVersion4.1
SHA-13DDE99BDA8ABD93C2348A4DC5CFC14BFE7EAE939
SHA-25655D0010AD87077BEB76320BB2C466999F9E806E0CF2400905DA81842502EDCC2
Key Value
MD551AE9911250504C9E5CF3B76CC525196
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.fc16.1
PackageVersion4.1.3
SHA-1BFB73562C1C898D3E49688A481BDA542C22F8317
SHA-256FA0096C49122A7023D961CEEF2F65348F6E488897AD9DA7F5E36E8C01ECE23A4