Parents (Total: 8)

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

Key	Value
MD5	E0846CD7B7CFFC32A8107C85503CBBFE
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	CloudLinux Packaging Team <packager@cloudlinux.com>
PackageName	httpcomponents-core
PackageRelease	3.module_el8.0.0+6004+2fc32706
PackageVersion	4.4.10
SHA-1	697BBAAB0BEC9D9C8440290C95456FEB8A14CDC1
SHA-256	3CFB0CE88ACE9D19FA863204DAE0BFD282EA609BC3BCE361F29D573F6FD48FAD

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	0ED2E72A8A8F39FA9FF166B3FE3CCCEC
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.5.0+922+9f7ad99e
PackageVersion	4.4.10
SHA-1	2AC67537840C0A70857C2FBCD390B2D7F7D99855
SHA-256	8A7786BCFFFCB65AFADDAAE274890236F1428C5E04C14FF59C1AB6C351E0F917

Key	Value
MD5	90556DEBD60B959F86EE0AC81DF6138A
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.0.0+39+6a9b6e22
PackageVersion	4.4.10
SHA-1	AED63847240149B34445E74327A60139A81D38B8
SHA-256	6CC542BF13FE03CE204BB071EB25A3105CB82FD40832C13CFD1979DF59F7F877

Key	Value
MD5	A3AB5792FA2F3EDA4786A5A38FAF52F4
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	CloudLinux Packaging Team <packager@cloudlinux.com>
PackageName	httpcomponents-core
PackageRelease	3.module_el8.0.0+6035+97aff910
PackageVersion	4.4.10
SHA-1	EAB364BF9AD3420ABB55AA9452F5F06CE7CAF9F8
SHA-256	8C41C828CF30B672FDDA4C830E4D95520D701142AAB09788769F902177D30146

Key	Value
MD5	0084B5CA08A9F0B589775DC44F0C1E3B
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.0.0+30+832da3a1
PackageVersion	4.4.10
SHA-1	05C1A86D175602CD910F08309801CAB8D02D86DC
SHA-256	C30A712AA63F64267ED65AD202D1BD2194A8D430D7D64A538784EAC8D88BEDA0

Key	Value
MD5	54A3D6887C230544FF325C3AFA8DA3DB
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	daviddavid <daviddavid>
PackageName	httpcomponents-core
PackageRelease	1.mga7
PackageVersion	4.4.10
SHA-1	2F1CB86CD1845DDF2816E44A2C0350BD0AE688BD
SHA-256	B2A90C2C33AB54E476D20AE311C07B075C0D5C8A992B7F35649862EDD97FDA0C

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