Re: Again, sorry, caching.

Jeff Davis <list-pgsql-hackers(at)dynworks(dot)com> writes:

> A library implies that the application is running long enough to actually
> hear the notofication. Web apps start up, read from the database, and before
> any cache is needed they're done and the next one starts up, reading again
> from the database. Only currently open connections receive the notification.

If your web app works this way than you already don't care about
performance. People doing scalable web apps these days use connection
pooling and session data kept in memory, so you already have a
persistent layer running (whether it's your JVM, Apache process for
mod_perl or PHP, or whatever). Really big apps definitely have a
long-running daemon process that handles caching, session management
(so you can have multiple webservers) etc etc...

-Doug
--
Doug McNaught Wireboard Industries http://www.wireboard.com/

Custom software development, systems and network consulting.
Java PostgreSQL Enhydra Python Zope Perl Apache Linux BSD...