We use a home grown diconnected resultset to store the data between request. (That was developed before there was something like the RowSet available)
Have a look at the following link about a disconnected RowSet: http://developer.java.sun.com/developer/technicalArticles/javaserverpages/cachedrowset/ If that's possible for you to use it, depends on the size of the result sets and the functinality that you need. The disadvantage is, that you either lose the ability to lazy load the results, or the implementation of the disconnected resultset get much more tricky. > -----Original Message----- > From: Reynir H�bner [mailto:reynir@;hugsmidjan.is] > Sent: Thursday, October 31, 2002 7:22 PM > To: Tomcat Users List > Subject: RE: JDBC / ThreadLocal pattern. > > Craig worried about having a transaction per user session > which would be very expensive and wouldn't scale beyond > internal testing. However, in the general case, we'd close > transactions at the end of a request. Some times, however, a > user asks for a list of items matching a set of criteria and > we'd then keep the Connection until the user moves away from > the list of results. We'd have a read-only ResultSet from > which we'd lazy-load data as the user pages through it. > > Is there a better way of implementing this kind of > functionality that doesn't entail committing a connection to it? > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
