Connection pool [moved]

[lvca]

This is Issue 70 moved from a Google Code project.
Added by 2010-07-22T09:15:44.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-Low, v0.9.21

Original description

OrientDB needs a connection pool like RDBMSs provide. Since the aim of the connection pool is to leave the connection open to minimize, as far as it can, the overhead of the creation, opening and loading of the schema.

The API could be something like:

ODatabaseDocument db = ODatabaseDocumentPool.acquire( "remote:localhost/demo", "admin", admin" );

...

db.close();

---
The API ODatabaseDocumentPool.acquire() should return a wrapper of ODatabaseDocumentTx class that override the close() method to release the instance to the pool.