Steven,
Have you noticed performance decline by doing this? I have thought about
implementing an RMI solution for my connection pooling, but decided against
it because my worries with performance. Any info would be appreciated.
-Todd
>From: "Costello, Steven" <[EMAIL PROTECTED]>
>Reply-To: "A mailing list for discussion about Sun Microsystem's Java
> Servlet API Technology." <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: db connection pooling strategies
>Date: Mon, 24 Jul 2000 10:37:24 -0400
>
>I'm not sure if this satisfies your application goals, but what we did was
>make a database manager as an RMI server. As part of the db manager, it
>incorporates the use of a db connection pool. We have both servlets and
>applications that make database requests to the database manager as RMI
>clients. Hence, they are both utilizing the same database connection pool
>and database access routines... Hope this helps.
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
