Key | Value |
---|---|
FileName | ./usr/share/maven-metadata/httpcomponents-core.xml |
FileSize | 2689 |
MD5 | 3E79E4643AA8FDEDB37622AB99F6D954 |
SHA-1 | 9847D8AF7C601B4C105FC79AAF106E2A8FD0B4D3 |
SHA-256 | A70C8C3C9704C15B5E53D0A5A6AA68F9A8D94E37D62D5FAB46473B5BDA2D0072 |
SSDEEP | 48:cmAcRtZNdVWhYYaty2VT5CatydVTCatR2VIpKCSINysVK7hatRdVSKXCSINysVKY:LAuPVYa7h5Cae1CaqCsCSIbuaxkwCSI5 |
TLSH | T1AB5117F4A9FD507172940AC0DE72AAA3EFD4D0B7E8915588B0CE45C98FCADCA81B3156 |
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 | 9F9CE7F941FA813F7F2AD716BA67BF04 |
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 | 3.module_f29+6921+ca3ed728 |
PackageVersion | 4.4.10 |
SHA-1 | B215941B5D7892322D0CBD855912A11D9E1DCED0 |
SHA-256 | 31C940AC8239F5881C5C1D2C177BAB65BA2E30824AAAB41B84E176AD2F5C0DCD |
Key | Value |
---|---|
MD5 | 3BCBE84ACB8BAD860330E7611F4D6117 |
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 | 3.module_f29+6921+ca3ed728 |
PackageVersion | 4.4.10 |
SHA-1 | 4ABC50750D103B20C358AAC46C6B7D40CE7A26C8 |
SHA-256 | 8850AB0383EFCF24E364E7F3E265007231F94E00A708A741C7C4E36F68502CAE |