Result for 4752EF7BA26AB1AB7A3A68C73E9A2A476881677B

Query result

Key Value
FileNamejakarta-commons-dbcp.spec
FileSize14352
MD51B8BDD257E33C9D4007EDE7EBFEBDEA9
SHA-14752EF7BA26AB1AB7A3A68C73E9A2A476881677B
SHA-256095EB0638D8E3A2459F08CC0038F8152A013464633D9D3741F310D750BF7A436
SSDEEP384:WrskrsT2jqsSsEhH6EXwqqnHAHOEjb8WZMoxYwtHBdzDhucVZmKro:WTrjqaE1egTjb8WZMoxYwtX//VZq
TLSHT1C352093732C0D537E8C75BC1EA3477406767822B698BB47871ACA744139B489D2FA07B
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
MD54AB7A40BD1C421FEA60DD9745D0AA89E
PackageArchia64
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
PackageRelease11jpp.3.fc9
PackageVersion1.2.1
SHA-12511F8EB3711A2D19E29A98069F094727C61CB60
SHA-256F4A7B67215BB21EADDBE7734C49C9691705CEAB2897F23D1334EED98FE681C37
Key Value
MD5360D0E4E8731CF03A22ABFA5BFB2CC58
PackageArchsparc64
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
PackageRelease11jpp.3.fc9
PackageVersion1.2.1
SHA-1FE8D91B8FF2972986EB409CE48AA9BC7E5ADFB88
SHA-256B521C7E2DB47FEECBD973E1971A432C6DB06D0C68B3547E31B19A62E8EA77A70