[plt-scheme] concurrent database connections

I can't comment on what works best, but I can say that nothing in the
web-server prevents you from implementing any of those options.

For different sessions to use the same connections, they must servlet
module-level definitions.

For different servlets to use the same connections, there must be a
single module that handles the connections that is shared via
make-servlet-namespace.

Jay

On Wed, Mar 25, 2009 at 2:31 PM, YC <yinso.chen at gmail.com> wrote:
> Hi all -
>
> I am wondering what the experiences is in handling concurrent database
> connections, say with web-server and SPGSQL.
>
> Do the web-server threads
>
> owns its own connection
> share a single connection
> share a pool of connections
> any other approach?
>
> Since postgresql probably cannot support unlimited connections, it seems
> having a connection pool might be the proper choice here, but I am wondering
> whether people have experiences with any of the approach and can share
> thoughts on the subject.
>
> Thanks,
> yc
>
>
>
> _________________________________________________
>  For list-related administrative tasks:
>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
>



-- 
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://teammccarthy.org/jay

"The glory of God is Intelligence" - D&C 93