Result for 53EC76F667CE33BBA04A92A969A0456C91DFC6D3

Query result

Key Value
FileName./opt/rh/rh-maven33/root/usr/share/doc/rh-maven33-httpcomponents-core-4.2.4/RELEASE_NOTES.txt
FileSize46636
MD59ECB034C9DD512145C7823DA923488C2
SHA-153EC76F667CE33BBA04A92A969A0456C91DFC6D3
SHA-25691B60BD55553EEF78855ECA710D137325FD7BB5705E41EA6924B9A697AA5F269
SSDEEP768:B/cyPj5DuiPTuh12Z0edjL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKg19Z+:mGPaT2VIxwuCfZWW6CfSzs8
TLSHT1A42362313E4933350E13E4D7DBC39541EBF9A89CE7A554F2958CC41C229A8A892BF7D8
hashlookup:parent-total7
hashlookup:trust85

Network graph view

Parents (Total: 7)

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

Key Value
MD598FCEF3FFAC183C5B03F422719FB6990
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.fc19
PackageVersion4.2.4
SHA-13FA09345C76629D2A2B3C4FF71B01FE1005046E1
SHA-256D5D13348ED28683560B0E2C483622C8D6913B077B79FA0779F984EB10493291B
Key Value
MD5ED4FE72CDEAC93FB84844F3ED8BD8F87
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
PackageRelease5.fc20
PackageVersion4.2.4
SHA-1E928D9263910169485F92829E8F1BF78322E3211
SHA-2569A0C6A9657F7C88B5737D96D100562B2217DF442F9E36E5F2FA07DDED8E02C61
Key Value
CRC32FEE36103
FileNamehttpcomponents-core-4.2.4-6.el7.noarch.rpm
FileSize476764
MD58BAF46327997B607531EBC38B91A45B9
OpSystemCode362
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 BuildSystem <http://bugs.centos.org>
PackageNamehttpcomponents-core
PackageRelease6.el7
PackageVersion4.2.4
ProductCode202232
SHA-1E56DB1417AE92102D5F02A3780EC11FD8CB408B1
SHA-256A33F4D3B295171C9C4E31903A3627E48650FBD63DA4865D2E16528C5CA9D1546
SpecialCode
dbnsrl_modern_rds
insert-timestamp1647061811.9994073
sourceNSRL
Key Value
MD5256E0F4DB28306DF551ECA3377B72BD4
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.fc19
PackageVersion4.2.4
SHA-10FC7E58CE44E56F482F2C3488BE3E662BC7B55BF
SHA-25647CA532F531D75B1B13BF55F2BD9E4BE624741592F983412A1659D0E99BE4DA0
Key Value
MD5C38C56EDCD8BDC7F9AF61E3301F4A191
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.fc19
PackageVersion4.2.4
SHA-11412EBF92CC45D470FD024305C053EB096FC3233
SHA-2564AF6DA82256FC797397F5E01A22ABF69CA732BC81819AC1FDE4E575A38C7DEFE
Key Value
MD5C178CDCFC889F9859297B1F77C8B2CEE
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
PackageRelease5.fc20
PackageVersion4.2.4
SHA-1CA3CE3A386D272818B894F696580831ACFFE67A6
SHA-256A562688ECE9B6D355711C7F312BE05AA141D33106BFD86CB14C4616240C6F94A
Key Value
MD5834F8CDBA0F7FE376E9ABAB9D54578EC
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>
PackageNamerh-maven33-httpcomponents-core
PackageRelease6.14.el7
PackageVersion4.2.4
SHA-1529FCBBBBA0F1547B2B5D3A1F71FC5E16B28F7E8
SHA-25630348A396E7925A449C019B1DF4EE3517F6755D8C95C5762533EF9B2C100D059