--- Frank Replies to my inquiry ---
> The rub with CGI is statelessness.  You can minimize the
> startup cost by
> holding the database(s) open with another program.  You can eliminate
> database startup costs by having that "other program" do all
> the database
> work while maintaining communication with each newly launched
> CGI.  This
> communication can be as simple as a message or pseudo-message
> file or as
> complicated as you wish.

While the DB is open just about all the time (via online sessions/jobs), I
don't know that I'd ever be comfortable with each cgi invocation opening and
closing it.  Thus, I'll probably rely on other methods as suggested via
replies.

Is anyone doing this that would care to share their experience?

jds