"Subrahmanyam A.V.B." wrote:
> - Thirdly, see if you can build an RMI server to do the database access
> including result caching. Since this RMI server will run outside the
> container process, you can have daemon theads to fetch the results from
> the DB, and update the cache. All your clients (servlets) can fetch
> results from this server.
>
Or, use an EJB server. Entity beans do pretty much exactly what the original
requestor asked for with regards to caching results for multiple users
simultaneously. There's no reason to invent anything extra.
> Subrahmanyam
Craig McClanahan
___________________________________________________________________________
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
