Result for FB28C853706D90BA6B642710A85854CC137CF684

Query result

Key Value
FileName./usr/share/doc/packages/httpcomponents-core/RELEASE_NOTES.txt
FileSize72758
MD5EB8D2B7ABBEF4DD70F195EB5EBD51470
SHA-1FB28C853706D90BA6B642710A85854CC137CF684
SHA-25649AC753F8ADC2B25DE02E0E016019D41FEFAAA2586599BBEF68333F08867B77F
SSDEEP768:0+jRWuycsRccdb7fhxrInd2X0kdjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKg1y:LPUxsd2tIxwuCfZWW6CfSzs8
TLSHT1876394317E9933350E13D5E7DBC35501EBF9A89CD7AA54F25A4CD00C219A8A882BF7D8
hashlookup:parent-total10
hashlookup:trust100

Network graph view

Parents (Total: 10)

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

Key Value
MD5E0846CD7B7CFFC32A8107C85503CBBFE
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.
PackageMaintainerCloudLinux Packaging Team <packager@cloudlinux.com>
PackageNamehttpcomponents-core
PackageRelease3.module_el8.0.0+6004+2fc32706
PackageVersion4.4.10
SHA-1697BBAAB0BEC9D9C8440290C95456FEB8A14CDC1
SHA-2563CFB0CE88ACE9D19FA863204DAE0BFD282EA609BC3BCE361F29D573F6FD48FAD
Key Value
MD59F9CE7F941FA813F7F2AD716BA67BF04
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
PackageRelease3.module_f29+6921+ca3ed728
PackageVersion4.4.10
SHA-1B215941B5D7892322D0CBD855912A11D9E1DCED0
SHA-25631C940AC8239F5881C5C1D2C177BAB65BA2E30824AAAB41B84E176AD2F5C0DCD
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
MD590556DEBD60B959F86EE0AC81DF6138A
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+39+6a9b6e22
PackageVersion4.4.10
SHA-1AED63847240149B34445E74327A60139A81D38B8
SHA-2566CC542BF13FE03CE204BB071EB25A3105CB82FD40832C13CFD1979DF59F7F877
Key Value
MD57DA0BA2627DF09E946344A76A1616DCD
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamehttpcomponents-core
PackageReleaselp152.1.1
PackageVersion4.4.10
SHA-17EB6BE0E0618C030DAA19C1854AA13946B56F4BC
SHA-256BD78EB11E1C109A8908D38BB1B8ED7CF6DD69C4B671877BE4BC2DB2C640F8C0C
Key Value
MD5A3AB5792FA2F3EDA4786A5A38FAF52F4
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.
PackageMaintainerCloudLinux Packaging Team <packager@cloudlinux.com>
PackageNamehttpcomponents-core
PackageRelease3.module_el8.0.0+6035+97aff910
PackageVersion4.4.10
SHA-1EAB364BF9AD3420ABB55AA9452F5F06CE7CAF9F8
SHA-2568C41C828CF30B672FDDA4C830E4D95520D701142AAB09788769F902177D30146
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
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
MD570DE2A3780408AB8511E73348F968D48
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.
PackageMaintainerhttps://www.suse.com/
PackageNamehttpcomponents-core
PackageRelease3.2.6
PackageVersion4.4.10
SHA-1D12E77C032B09039F917C8EF8D7EB7202A179C87
SHA-2566AE4864C5CD108ABB354EEEA9CF9775182B0AE7C1929B831B48A58AF71C83345
Key Value
MD53BCBE84ACB8BAD860330E7611F4D6117
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
PackageRelease3.module_f29+6921+ca3ed728
PackageVersion4.4.10
SHA-14ABC50750D103B20C358AAC46C6B7D40CE7A26C8
SHA-2568850AB0383EFCF24E364E7F3E265007231F94E00A708A741C7C4E36F68502CAE