Result for 70D3A0BA5CF99552490D3FC4D9E017757418A049

Query result

Key Value
FileNamejakarta-commons-dbcp.spec
FileSize11994
MD50858AE7B3736FFFADB5C31E9F50699BC
SHA-170D3A0BA5CF99552490D3FC4D9E017757418A049
SHA-256B7B129BF55A83FEB17DB3C41C1C4E46BD6E59A96926CECE2674F093C7330A2C7
SSDEEP192:6DrskrsTE3L3qmJ3sxL6pd1lTI1BptojnHAHO8MoAsYZaW3BOvTORWhuXyerT5dB:WrskrsT2jqsscGxtojnHAHO8MoxYwWuG
TLSHT15D32093B21C0E63B95838BD9AA34B7449767412BA597A4BC717C678013AB4CDD27F03B
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD54120D48F23B137CA35C795FF4A860AAC
PackageArchnoarch
PackageDescriptionMany Jakarta projects support interaction with a relational database. Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfeasible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally.
PackageMaintainerFedora Project
PackageNamejakarta-commons-dbcp
PackageRelease13.7.fc12
PackageVersion1.2.1
SHA-11BD976F1136E0F72473F9248400D780D7B7A6A63
SHA-256EB13A688DAA52789B02C840FBE81D900003FB8E6244C71146E179D2AC941B643
Key Value
MD5EDBF37C23A5C2B98F54F003466B63683
PackageArchnoarch
PackageDescriptionMany Jakarta projects support interaction with a relational database. Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfeasible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally.
PackageMaintainerFedora Project
PackageNamejakarta-commons-dbcp
PackageRelease13.7.fc12
PackageVersion1.2.1
SHA-1A8D5AA4B80AE5F4C73B77061FE3B3DC76C4EE609
SHA-256326D70001D253241D434470AEB1F00C9FB9132F268647B7807142055928F3149