Key | Value |
---|---|
FileName | ./usr/share/maven-metadata/httpcomponents-core.xml |
FileSize | 1827 |
MD5 | 0915715FBEE89109591BCCBE68803DC6 |
SHA-1 | 6FC705C84982250E37D31A56B2FDB45DEBF0B60F |
SHA-256 | 4F9A5328E18E6D41D07B3A16FA90989D0B034DC7EA92734DFF3A5A61E6B7505E |
SSDEEP | 48:X5pLRbXbb7VKw03qDsRbXbi7VAw03qDsRbMbbVZw03qDsRbMbi7Vbw03qDxm:X5P7gPE76PAHPX7lPh |
TLSH | T13431A2EE51FCA83E268E8D809F33B492EFD5A0E7D4494594B1CE84680FDE9D52123DD2 |
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 | 70DE2A3780408AB8511E73348F968D48 |
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 | https://www.suse.com/ |
PackageName | httpcomponents-core |
PackageRelease | 3.2.6 |
PackageVersion | 4.4.10 |
SHA-1 | D12E77C032B09039F917C8EF8D7EB7202A179C87 |
SHA-256 | 6AE4864C5CD108ABB354EEEA9CF9775182B0AE7C1929B831B48A58AF71C83345 |
Key | Value |
---|---|
MD5 | 7DA0BA2627DF09E946344A76A1616DCD |
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 | https://bugs.opensuse.org |
PackageName | httpcomponents-core |
PackageRelease | lp152.1.1 |
PackageVersion | 4.4.10 |
SHA-1 | 7EB6BE0E0618C030DAA19C1854AA13946B56F4BC |
SHA-256 | BD78EB11E1C109A8908D38BB1B8ED7CF6DD69C4B671877BE4BC2DB2C640F8C0C |