Thank you all again.
The reason behind my initial approach was that I thought time spent for I/O
operations on the server side would be insignificant compared to the time it
takes to down load something of which upto 90% may be irrelevant. I forgot to
mention but the site is not expected to be a high access site and concurrent
access is not expected either.
Anyways, I'm now certain that I will use the fourth approach recommended by
Craig. I'll probably have a hidden field on the generated page containing some
kind of a pointer to the current row in the "ResultSet". Every time next/prev is
pressed, some JavaScript will take care of incrementing/decrementing this index
accordingly.
Thanks,
Yuki
______________________________________________________________________
This E.Mail is confidential and intended for its addressee only. If you have
received this in error, please delete it from your PC and inform us by
telephone.
No reliance may be placed upon this E.Mail without written confirmation of its
contents and any liability arising from such reliance without written
confirmation is hereby excluded. Copyright in this E.Mail remains with the
Sumitomo Bank Limited
___________________________________________________________________________
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
