Connection Pooling

This follows on from the discussion in the advocacy thread , but I didn't want to mess up that thread with on topic posts

What I want to do is use SRM for database connection pooling, as any J2EE application server would. PHP does handle persistent connections, but this (as Rycamor has pointed out) is not the same as connection pooling.

A php script would grab a connection and release it at the end of the script, without the overhead of creating and freeing the database connection. SRM would mantain a pool of database connections, monitor the number of used connections and create new connections when the number of needed connections exceeds the current pool.

I was chatting with Jonathan Arkell (SRM dude) about getting connection pooling going with SRM. It looks like it will be a whole lot harder than I thought, so hopefully I can persuade him to give me a hand

There are two obstacles to overcome:
*Passing db connections back and forth
*Maintaining the pool of connections as threads

SRM cannot pass resources (such as db connections) back and forth, so he was saying he'd look at the eclipse abstraction library and see how they do it.

The other problem is that SRM is not multi-threaded, so have the pool of connections available is also a problem. He suggested with the declair() construct it would be possible to give threads to PHP. I read the manual on it and the examples and that looks like it will work although:



I was just wondering if anyone had had any experience in either of these areas and could offer some advice

Thanx heaps, Z.