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
MD5	4120D48F23B137CA35C795FF4A860AAC
PackageArch	noarch
PackageDescription	Many 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.
PackageMaintainer	Fedora Project
PackageName	jakarta-commons-dbcp
PackageRelease	13.7.fc12
PackageVersion	1.2.1
SHA-1	1BD976F1136E0F72473F9248400D780D7B7A6A63
SHA-256	EB13A688DAA52789B02C840FBE81D900003FB8E6244C71146E179D2AC941B643

Key	Value
MD5	EDBF37C23A5C2B98F54F003466B63683
PackageArch	noarch
PackageDescription	Many 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.
PackageMaintainer	Fedora Project
PackageName	jakarta-commons-dbcp
PackageRelease	13.7.fc12
PackageVersion	1.2.1
SHA-1	A8D5AA4B80AE5F4C73B77061FE3B3DC76C4EE609
SHA-256	326D70001D253241D434470AEB1F00C9FB9132F268647B7807142055928F3149

Key	Value
MD5	4AB7A40BD1C421FEA60DD9745D0AA89E
PackageArch	ia64
PackageDescription	Many 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.
PackageMaintainer	Fedora Project
PackageName	jakarta-commons-dbcp
PackageRelease	11jpp.3.fc9
PackageVersion	1.2.1
SHA-1	2511F8EB3711A2D19E29A98069F094727C61CB60
SHA-256	F4A7B67215BB21EADDBE7734C49C9691705CEAB2897F23D1334EED98FE681C37

Key	Value
MD5	360D0E4E8731CF03A22ABFA5BFB2CC58
PackageArch	sparc64
PackageDescription	Many 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.
PackageMaintainer	Fedora Project
PackageName	jakarta-commons-dbcp
PackageRelease	11jpp.3.fc9
PackageVersion	1.2.1
SHA-1	FE8D91B8FF2972986EB409CE48AA9BC7E5ADFB88
SHA-256	B521C7E2DB47FEECBD973E1971A432C6DB06D0C68B3547E31B19A62E8EA77A70

Key	Value
MD5	29131C84DB606AF0D095F6F3F0FFE7FB
PackageArch	s390x
PackageDescription	Many 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.
PackageMaintainer	Fedora Project
PackageName	jakarta-commons-dbcp
PackageRelease	12.5.fc11
PackageVersion	1.2.1
SHA-1	D0D0DEACFC0F61E2611C9D4F6198D4BB2984B3E8
SHA-256	90C2BF33FFC4F02E16D9150CE103988C65297D8C5C0C207DA649EC1004565C82