Result for 8003243416D1938259548DB281EEAEEECAD3B9BC

Query result

Key Value
FileName./usr/share/doc/packages/httpcomponents-core/RELEASE_NOTES.txt
FileSize78777
MD5C1EA913F4B1AFF0A7C14BEB2C6FD3F09
SHA-18003243416D1938259548DB281EEAEEECAD3B9BC
SHA-256C7D1FFF57370D340944D223E78D1D66E63FF7AC4420A45496C5C3BF5B5B8F9E9
SSDEEP768:zKGsJ+jRWuycsRccdb7fhxrInd2X0kdjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllc:+P8PUxsd2tIxwuCfZWW6CfSzs8
TLSHT1B47394317E9D33350E13E5E7DBC35501EBF9A85CD7AA54F25A4CD00C219A8A882BF6D8
hashlookup:parent-total15
hashlookup:trust100

Network graph view

Parents (Total: 15)

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

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
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
MD599B2033A8F41A5DCCEF4F3149747D43B
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+10775+1e739c8d
PackageVersion4.4.13
SHA-176BD52022BD4C014C5822C66EE2C6F02C68621DD
SHA-25639B94178B193582AA78293C2B3EF5DCBE78A6E9AB439F48B7B7B8D6A5CD9B767
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
MD5A7E69B4531D360B4804FD001BE8CB386
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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamehttpcomponents-core
PackageRelease4.2.el8s
PackageVersion4.4.13
SHA-186F25B014FD4D29C766A6989045ADFB4D69B9C57
SHA-2562EC50BF182ED5448869FDD4801AD2D9045BACD99C54ABE5FBBDD9E0BF24BE01E
Key Value
MD53748951EF5B521AC70481660C3D982CF
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+10783+5131ca6c
PackageVersion4.4.13
SHA-17615D634022ACBC39FF91D619AA936EC4AE949C2
SHA-25645995F78E7270BC73E1C9694CAAB0B474F73A23CBA542B758B612C66C98FC445
Key Value
MD5448C596F8526EF01A1C774CB82C411E7
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
PackageRelease150200.3.6.4
PackageVersion4.4.13
SHA-1B2C774CDD1272B8B4831754FFA7B2A94819975B1
SHA-256E6C0FAE692DF1A8657D84EEE6306A2ADF4CA0843B24A8C23CBF3258B07B87EE1
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
MD53015C3F0B9A20E3E9ED2F14E11463744
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
PackageRelease3.mga9
PackageVersion4.4.13
SHA-1F55D3DB371F0FC8DA6BAE8581375280AB617C174
SHA-256848BCCFF244A405F68AB474B54B25230BD204A0D4F4758A6C0AAAD9E83D94B22
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