Result for 90C6605E4E1FE4A1FC7AF09CBB31E27AA9532ED6

Query result

Key Value
FileName./usr/share/doc/packages/httpcomponents-core/README.txt
FileSize2149
MD5176F7F4FC0D54BD109F3CC86653B3587
SHA-190C6605E4E1FE4A1FC7AF09CBB31E27AA9532ED6
SHA-25667F16721CCCFA38359C3432646413F34B538212AE112C6ECB72F1C92A1C9A796
SSDEEP48:B79KcqkAJE9RqZyYiHED6aXNLQCEg9ek9XQe:B79KoAJE9Rq3iHseCEg979L
TLSHT19B418717BD2CA73111E2C3A06BB69455FBBF6798F285212CEC1642706315FE4C67F1A4
hashlookup:parent-total40
hashlookup:trust100

Network graph view

Parents (Total: 40)

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

Key Value
MD50084B5CA08A9F0B589775DC44F0C1E3B
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNamehttpcomponents-core
PackageRelease3.module_el8.0.0+30+832da3a1
PackageVersion4.4.10
SHA-105C1A86D175602CD910F08309801CAB8D02D86DC
SHA-256C30A712AA63F64267ED65AD202D1BD2194A8D430D7D64A538784EAC8D88BEDA0
Key Value
MD50ED2E72A8A8F39FA9FF166B3FE3CCCEC
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNamehttpcomponents-core
PackageRelease3.module_el8.5.0+922+9f7ad99e
PackageVersion4.4.10
SHA-12AC67537840C0A70857C2FBCD390B2D7F7D99855
SHA-2568A7786BCFFFCB65AFADDAAE274890236F1428C5E04C14FF59C1AB6C351E0F917
Key Value
MD554A3D6887C230544FF325C3AFA8DA3DB
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerdaviddavid <daviddavid>
PackageNamehttpcomponents-core
PackageRelease1.mga7
PackageVersion4.4.10
SHA-12F1CB86CD1845DDF2816E44A2C0350BD0AE688BD
SHA-256B2A90C2C33AB54E476D20AE311C07B075C0D5C8A992B7F35649862EDD97FDA0C
Key Value
MD5F374C869F9A5A65056A84A54F0675E7F
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.module_f34+10793+8c309e06
PackageVersion4.4.13
SHA-130AD8DAB9FBD1FF16A34351C2DD164F902FDBF2A
SHA-2566F55F1E4A1EC264554BAB3ECCCB626D762CD6146BE70C21D37C6C41A5A413D52
Key Value
MD58448844877E55454CB0D565CF066F125
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease1.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-13324424E045A841626772C9E1A756FCF2B3E0038
SHA-25654126A46046CE827DCBF57429DD76F202ABFFFBF3BC7CB8C04011EF40D1CC41D
Key Value
MD57B79270DFC02F7F7ED2A4EA260017384
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.fc24
PackageVersion4.4.4
SHA-1395C678A3580233A779BDAFB98C51238992ADC71
SHA-2561866D4EA6DE080FE040DC7F1F79335523429595E05217547699C61BB1D14114C
Key Value
MD52B1D0D8D551E22D7035244E389229716
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerneoclust <neoclust>
PackageNamehttpcomponents-core
PackageRelease1.mga8
PackageVersion4.4.12
SHA-13D6CEDE174E6E0262B8CA35954A4E5CF3221E547
SHA-256ED5511DF27DCE6982A4A1948C4BB47746AB74B69F9C39BC47323F3EB5ED64AD0
Key Value
MD50A7A208353AA490E510AAC405AB86CC8
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.fc23
PackageVersion4.4.1
SHA-14034B47CF9FC29FAAA457A76382FA880B53D0602
SHA-256F69F09B9ED2B606CA04818219BE5BFDEBFF5EDCE52B85886F07D280F57FE847F
Key Value
MD5997BF7F16FFF3F64ED535A27BC4D7043
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease4.fc33
PackageVersion4.4.12
SHA-143A1E428F9AF496DFFBE783321AFB41D9A5FA829
SHA-2563686F47B8089E00409394BAD8BF7552B8F26BAD43B0B0EA6FBF2CA576A2219D3
Key Value
MD5C335BADB1A9F4F3B9FD4B3003D071727
PackageArchnoarch
PackageDescriptionHttpCore 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.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease2.fc32
PackageVersion4.4.12
SHA-14764652AECD392AE43D59FFFFDC18915699C18E6
SHA-2569DA620A39FD22DC655860276400719AD702B5A73D88254FBDECCFB76B1832729