Re: persistent DB connections (was: RE: modular database backends)

[Peter Novodvorsky]

Hello!

You're speaking about _new_ backend daemon. We could make a lot of backend
daemons, but it is second stage, IMO. 

Any daemon has fixed language (protocol) in input and modular in output. 
What you are talking  currently is rewrite of GNATSD.

Dirk Bergstrom <address@hidden> writes:

> 1) keep the current model, adding a separate, persistent, "database daemon".
> each connection would spawn a new instance of gnatsd, which would connect to
> the database-daemon as needed.  i happened across sqlrelay
> (http://www.firstworks.com/sqlrelay.html), a GPLed package which appears to
> do just what's needed for the database daemon.

This is most simple, and IMO, first that should be made. 

> 
> 2) a persistent daemon that handles setting up the connection to the client,
> and holds open a connection (or several connections) to the database.  as
> new requests come in, the daemon would fork off a child to handle each one,
> up to some preset limit.
> 
> 3) something like apache -- a master process forks several persistent
> daemons, which take turns handling connections.  each child daemon holds a
> database connection, and services many requests before shutting down.

Other approaches are good, but hey, do some BTS's handle more then 10 
connections  at  time? Really?

        Thanks,
-- 
Peter Novodvorsky     http://www.altlinux.ru/    AltLinux Team, Russia
Debian.Org                                       http://debian.org/~nidd
            Debian  ---  no need to  wait for tomorrow.