Key | Value |
---|---|
FileName | ./usr/share/maven-poms/httpcomponents/httpcore-nio.pom |
FileSize | 5660 |
MD5 | 88911751149BE53EB6563E448825F1D2 |
SHA-1 | CAE6C95247604EDE085B7632B11DCE790EE20EEA |
SHA-256 | 9EABD168227F45DA1322B17379C85C3AB7838812FE4CA23DF6EE2ECC0FDAD3A5 |
SSDEEP | 96:4QWR9VHFgRiFmHV9l4kM2gqQMj2B8oosvq8w45FeAt4lc9s:e9VHfFe9l4kM2gq32NosC25FeAtWc9s |
TLSH | T1FBC110B1DCFD54B2229105CAAB629482FFB9C1BBE0894148F48C87446F9DBCE41B7956 |
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 |