Parents (Total: 7)

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

Key	Value
MD5	D63606FDD4AE0BCBCF8FDE14009DDD39
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	AlmaLinux Packaging Team <sfokin@cloudlinux.com>
PackageName	httpcomponents-core
PackageRelease	2.module_el8.3.0+2032+25f04681
PackageVersion	4.4.12
SHA-1	849A982BFE71E36F75157278228E969011332302
SHA-256	70CF736CFA57A731BAA9BC94490A64AABBCC1F2596A8E4F4D53F8A24FC17B8B0

Key	Value
MD5	40DBEE5346ED437F334DB3425E96847B
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	CentOS Buildsys <bugs@centos.org>
PackageName	httpcomponents-core
PackageRelease	3.module_el8.4.0+652+27abba4b
PackageVersion	4.4.12
SHA-1	E2E30F44C522635907A34ED32AC71341A79A0BC1
SHA-256	B98D4DB6647E5E86109371C3A0EE3F0C69D574968994694B3ADE4731A9A7F0D0

Key	Value
MD5	C335BADB1A9F4F3B9FD4B3003D071727
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.fc32
PackageVersion	4.4.12
SHA-1	4764652AECD392AE43D59FFFFDC18915699C18E6
SHA-256	9DA620A39FD22DC655860276400719AD702B5A73D88254FBDECCFB76B1832729

Key	Value
MD5	2B1D0D8D551E22D7035244E389229716
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	neoclust <neoclust>
PackageName	httpcomponents-core
PackageRelease	1.mga8
PackageVersion	4.4.12
SHA-1	3D6CEDE174E6E0262B8CA35954A4E5CF3221E547
SHA-256	ED5511DF27DCE6982A4A1948C4BB47746AB74B69F9C39BC47323F3EB5ED64AD0

Key	Value
MD5	9E295F8C2D5424DD2ABA62A1AF87328D
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	AlmaLinux Packaging Team <packager@almalinux.org>
PackageName	httpcomponents-core
PackageRelease	3.module_el8.3.0+2039+157bd82e
PackageVersion	4.4.12
SHA-1	F0A29063AA88736D692B3CA5D4AEB04AB43F146D
SHA-256	27A3B4925C673EA4D114242B4BD3F9DFCC35DB2B2445C97BC980E7EFB08552CD

Key	Value
MD5	E59821F9DAE7267F157B22658617DA2E
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	5.fc34
PackageVersion	4.4.12
SHA-1	9BC54A43E74105F8228C6317D2F7831F790FBCE6
SHA-256	169194C0CB2C739C9B319492527BA9C4EBCC2FE8BB1FD0C16AA32C72E48C6537

Key	Value
MD5	997BF7F16FFF3F64ED535A27BC4D7043
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	4.fc33
PackageVersion	4.4.12
SHA-1	43A1E428F9AF496DFFBE783321AFB41D9A5FA829
SHA-256	3686F47B8089E00409394BAD8BF7552B8F26BAD43B0B0EA6FBF2CA576A2219D3