yup , you are right Andrei, ...this is really a common
problem and there is no standard design pattern to
resolve this.
Although, i came across a few frameworks which claim
they can resolve this issue but each of them missed
one thing or the other.
I ended up writing my own little implementaion to do
this.
In our case we had a biiiig resultset, but the query
itself takes a very short time...
so we wrote up a small paging implementation where
instead of having the open query [ which is not
recomended in a web tier app ] , we execute the same
query each time and skip to the record where we left
last time and get only X num of records. This will
definitely not kill any VM since it only creates X
data objects instead of the whole result set.
There is a trade off where we need to make more calls
to DB , but it is OK for us since our application
pages have ability to skip to a particular page in the
results and not have to traverse the whole list.
Again, like i said different requirements and
conditions require different implementations.
thanks
Nikhil Budhiraja
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
This archive was generated by hypermail 2.0.0 : Tue Jun 18 2002 - 14:37:40 EDT