process pools? (for gen_servers)

[Sean Hinde]

Pascal,

> Julian Assange writes:
>  > The context is persistant http connections. Tearing down the socket
>  > and rebuilding it for each url would be dramatically slower.
> 
> We had plenty of similar problems, and we ended up writing a generic
> 'pool_server' process which masquerades as a gen_server and
> load-balances requests to a pool of actual gen_servers.
> 
> Incidentally this pool_server is the right place to do things like
> load regulation (keeping track of how many requests there are in each
> server's queue), failover, static routing, retry-on-failure, etc.

We also find ourselves writing this "behaviour" quite often (though without
many of the nice features you describe here). Is this something which might
be abstracted from your proprietary code and contributed to the erlang
community (perhaps as the first of a growing pool of new R8 behaviours)? It
would certainly be a valuable addition to the contribs site.

Thanks and Rgds,
  Sean



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.