Re: Connection pooling.

At 23:10 11/07/00 -0400, Jeffery Collins wrote:
>It seems like a first step would be to just have postmaster cache unused
>connections. In other words if a client closes a connection, postmaster
>keeps the connection and the child process around for the next connect
>request. This has many of your advantages, but not all. However, it seems
>like it would be simpler than attempting to multiplex a connection between
>multiple clients.
>

Add the ability to tell the postmaster to keep a certain number of 'free'
servers (up to a max total, of course), and you can then design your apps
to connect/disconnect very quickly. This way you don't need to request a
client to get off - you trust the app designer to disconnect whenever they
can.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/