W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1997

Persistant DB Connections

From: Paul Walker <Paul_Walker@pegasus.us.dell.com>
Date: Thu, 11 Dec 1997 21:20:24 -0600
Message-ID: <3490AD78.6B35EEF0@pegasus.us.dell.com>
To: "www-jigsaw@w3.org" <www-jigsaw@w3.org>
Jigsaw Team,
    First thanks for all the great work!. Looks like I have found a
very flexable base from which to construct the system I am currently
designing. That system is basically an intranet query and analysis
system fed by serveral corporate db's.

After much experimentation with SSI, Servlets, etc, the dynamic
generation looks pretty straight forward. However, the key issue
I have now is performance. Specifically, I want to avoid the overhead
on each db server of making a db connection each time a page is
generated.


I would like to establish ODBC connections to each seperate
db server with one class and have it "broker" the queries and
deliver responses back to the calling resource, SSI, or Servlet.

I would like this connection to be persistant from server startup
through shutdown, with the necessary logic to re-establish
connection(s) if needed,  accessable via an  interface that can be used
by either an ssi command, servlet, or custom resource.

What is your vision for this level of functionality ?
Would a seperate "thin" or dedicated connection manager
or server be a easier path than adding this functionality to
Jigsaw.

Any thoughts, references, etc on this matter would be
greatly appreciated.

Thanks in advance,

Paul Walker
Dell Computer Corp.
Received on Thursday, 11 December 1997 22:26:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:27 GMT