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

[Michael Richardson]

>>>>> "Dirk" == Dirk Bergstrom <address@hidden> writes:
    Dirk> i, too, am inclined towards #3, but it does require rather a lot of
    Dirk> re-engineering.  under the current setup, gnatsd generally runs for 
only one
    Dirk> "transaction" (a search, a pr-edit, one gnatsweb hit, etc.).  turning 
it
    Dirk> into a persistent daemon would, to put it nicely, help us discover any
    Dirk> hidden memory leaks.

  Not necessarily.
  The "daemon" may consist of doing:

      1. open connection to database
      2. listen
      3. accept, fork process connection.
      4. loop

  + SIGCLD routine.
 
  The only thing that is being "preserved" is the connection to the database.
This depends upon the connection being one that can be shared. If it can't
be shared, then you get more into:
   1. open connection(s) to database
   2. listen
   3. while connection(s) available:
      accept, grab connection, fork, process
   4. loop
   + SIGCLD to return connection to available list.

Canadian Commuter Challenge Project -- GNU Potato Caboose 
Michael Richardson, Sandelman Software Works, Ottawa, ON  
EMAIL: address@hidden
for help, email or page at 1-866-231-8608