Result for 96C498B82B90AE9422CC7954BC74DCFB61E77DD5

Query result

Key Value
FileName./usr/share/maven-poms/JPP.httpcomponents-httpcore-nio.pom
FileSize5432
MD5B4849ADD0D36567A77D0BEA7B44D528D
SHA-196C498B82B90AE9422CC7954BC74DCFB61E77DD5
SHA-256AE797A5E682BB681EC01990BBC8D1210852200A5DBA8F181364E2DD912393374
SSDEEP96:PQWR9VHFgRyH2s9W4kMX5vFgGJbxMj2B8ceBAULAP4Atu5XB9s:/9VH4s9W4kMX5vFw2VeWUUP4AtuRB9s
TLSHT13CB163B4DCFD047113D409CA6B725483BFA9C1B7E0898248F49CA3469F5AFCB40B3966
hashlookup:parent-total5
hashlookup:trust75

Network graph view

Parents (Total: 5)

The searched file hash is included in 5 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
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