Result for C884845EC5D38CA06595A7765ADE8BE3DFC44389

Query result

Key Value
FileName./usr/share/maven-metadata/httpcomponents-core.xml
FileSize1827
MD58B50F4D78349BF8914DAD0D171E9846F
SHA-1C884845EC5D38CA06595A7765ADE8BE3DFC44389
SHA-25670C22D53A013B2B2A0C8E21DDF56A0E0C49A2ACADD2FB8FC221F94333FDDEAC8
SSDEEP48:X5pLRbXbb7eJiw03qDsRbXbi7eJIw03qDsRbMbbeJxw03qDsRbMbi7eJjw03qDxm:X5P7wiPE7wIPAwxPX7wjPh
TLSHT12331B7ED51FC643E358D8D809F32B492EFD5A0E7D4494594B1CE84680FDE9D92223DD2
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
MD51F65A6C859780FF03FD9DE5C6DBC921D
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.
PackageNamehttpcomponents-core
PackageRelease10.49
PackageVersion4.4.13
SHA-1CD22C494FD5ED7D0D934575C936C5AA6E1C60731
SHA-2567CF2F3DA92BF53DAD806A9F44D33DAF5E5EB87003F79D2F275774AB6E03D1512
Key Value
MD55E189CB0E7CB1A6528AA8B569E992EFA
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.
PackageNamehttpcomponents-core
PackageRelease10.60
PackageVersion4.4.13
SHA-1C88F58C9E83F85AA02CE5690A3B92F72EF128663
SHA-256AB86BA04E5ECA31DE1D66706B88077D05E5DC698875616C7A1EB0450E22FC57D
Key Value
MD5EC33771BD4A66324AB3F5B766282A638
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.
PackageNamehttpcomponents-core
PackageRelease10.51
PackageVersion4.4.13
SHA-160A8AC9F95FF7E3F9F38C872A458B5226733651C
SHA-2560550514A69F6182A0412F5097F15E114B0A3CCB3280E5DD9A848BC28228721EC
Key Value
MD5866CE9B321C37651A5C532F02131CD0F
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.
PackageNamehttpcomponents-core
PackageRelease150400.10.1
PackageVersion4.4.13
SHA-1A08911D9F04D962D3EFA523ED63DAD3B3EC5C64C
SHA-2561EA3C8B1C1B39976A7CBCE4C63889E66F8EDF64EB721EA9B00E593607BE079B0
Key Value
MD577A44219D407B1A7E1C59042CF2FB952
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.
PackageNamehttpcomponents-core
PackageRelease10.33
PackageVersion4.4.13
SHA-1EE3B0BE7FB16D6BAB1F194CD1BE8E129ED7D40F3
SHA-2568A4A5A986EAE2CBD9900963CD74173B9C2BEF27FCE5AE0F458EB07D9CF825EEF
Key Value
MD58C2EED800AD06C7EDA9EA151F72FD100
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.
PackageNamehttpcomponents-core
PackageRelease1.2
PackageVersion4.4.13
SHA-1E90F36FDF4D0397430A64074293050EAF7D2142F
SHA-2564A43974DF56728DE195A3E5D707BFD7F82F6806995DC8B5D2C0AA0CB59FC4B99
Key Value
MD57B43A507B231952EF617D111D95E8B1F
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.
PackageNamehttpcomponents-core
PackageRelease10.53
PackageVersion4.4.13
SHA-1F1653DF045F3D84A9F5D37E9DC3BF5429B9EB28B
SHA-2564E1C9B54B5D558EC7E9B90277425C4F844AF196D39BD17310011B5A5323D53A4
Key Value
MD519D0421E89D632DDC706DC36D94E1CF3
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
PackageRelease1.8
PackageVersion4.4.13
SHA-1ECFBB072AD9D781B6AB971BD6A115605F061EA5E
SHA-2568542BB211759B4A689CC1EA4E609D44784203250CA900031634271B32F6A6FCC
Key Value
MD5DB12C1D8F1A64EC365F762B393A51D77
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.
PackageNamehttpcomponents-core
PackageRelease10.74
PackageVersion4.4.13
SHA-1C0D0CAD45CC261EF171EDF70E9CA4CF74EF40413
SHA-256D45ADCBC74F8111BC0279B32EE8F2FA948ECE7FE9C59FCCE2BDC6968BBF093D2