"Donald E. Vandenbeld" wrote:
Yes, the resultset beans that I use have a session scope so they are dealt
with when the user either logs out or times out. The problem is one of
scalability. There are a a few resultset beans that could potentially be
quite large. If you multiply this by the
you can use applet bridge for calling your
server-side classes from JavaScript. It works
on the top of HTTP and Ok with firewalls.
See http://coldjava.hypermart.net/servlets/j2j.htm
Another way of doing it would be to use an applet and have the CORBA
connectivity directly between the browser and
sday, March 30, 2000 11:37 PM
Subject: Re: Returning large resultsets
"Donald E. Vandenbeld" wrote:
What I'm after is a methodology for caching a large resultset so that
you can 'page' through it and 'elegantly' being able to dispose of
the resultset cache when you leave the
What I'm after is a methodology for caching a large resultset so that
you can 'page' through it and 'elegantly' being able to dispose of
the resultset cache when you leave the resultset display page.
Did you try to use a cleanup method triggered by a JavaScript onUnload
event ?
/
--
From: Donald E. Vandenbeld[SMTP:[EMAIL PROTECTED]]
Reply To: Donald E. Vandenbeld
Sent: Monday, March 27, 2000 6:58 AM
To: [EMAIL PROTECTED]
Subject: Returning large resultsets
I have a question about implementation that I'd love some input
"Donald E. Vandenbeld" wrote:
What I'm after is a methodology for caching a large resultset so that
you can 'page' through it and 'elegantly' being able to dispose of
the resultset cache when you leave the resultset display page.
Did you try to use a cleanup method triggered by a JavaScript
Hi Donald,
It sounds like my Pager Tag Library is just what your looking for.
Check out http://jsptags.com/tags/navigation/pager/
-James
I have a question about implementation that I'd love some input on.
The Problem:
I have a web application that has to return variable length resultsets,
Actually, while you taglib looks quite interesting, it's not exactly what
I'm looking for. What I'm after is a methodology for caching a large
resultset so that you can 'page' through it and 'elegantly' being able to
dispose of the resultset cache when you leave the resultset display page.
It
I have a question about implementation that I'd love some input on.
The Problem:
I have a web application that has to return variable length resultsets,
sometimes quite large (a few 100 rows max). There are several tables that
might return large resultsets and each gets viewed in a different
