Key | Value |
---|---|
FileName | ./usr/share/doc/httpcomponents-core/RELEASE_NOTES.txt |
FileSize | 60576 |
MD5 | B5FBDAE6427E6E3AF1B8D56013CFF6BC |
SHA-1 | D8C015817C8055E69FB34791A8604B7E3F531C65 |
SHA-256 | 2823618CD88E8DBE339380604CDCB76EE46B7F4EAA2AA4FA2E82E73255BC3712 |
SSDEEP | 768:FycsRccdb7fhxrInd2X0kdjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKg19Z+:bUxsd2tIxwuCfZWW6CfSzs8 |
TLSH | T1264373317E4937350E13D4E7EBC35501EBFDA89CE7A954F2994CC01C219A8A892BF6D8 |
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 | 7B79270DFC02F7F7ED2A4EA260017384 |
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 | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 2.fc24 |
PackageVersion | 4.4.4 |
SHA-1 | 395C678A3580233A779BDAFB98C51238992ADC71 |
SHA-256 | 1866D4EA6DE080FE040DC7F1F79335523429595E05217547699C61BB1D14114C |
Key | Value |
---|---|
MD5 | 183D3888BA13C60DD7E30284E7AFCC20 |
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 | Fedora Project |
PackageName | httpcomponents-core |
PackageRelease | 2.fc24 |
PackageVersion | 4.4.4 |
SHA-1 | 80F3BC80852E79B5B38A13E52365D9CAB0B846F2 |
SHA-256 | 00356159C70ABC1557F2A1595F1682AF1A983D96A1A45DC4C804AE10AA4B7B6C |