Hi Jeff --
Once your jsp outputs its data, its job is done and
there is no opportunity for it to update anything.
The only way data can be updated is if the client
requests it, which means you'll have to force the
client to refresh. If it's a browser, set the
appropriate header or include the co
Adding to Justin's method, you can make this polling a more subtle event
by placing a polling jsp page in a frameset with your jsp page, but have
the polling page take up no visible space.
So in effect you divide it into 2 pages: the original data diplay page and
an invisible "polling" page that
Jeff,
The refresh request has to come from the user-agent. There is a tag that
you can emit into your section to cause the user-agent to refresh the
page periodically.
Alternatively, if you had an applet, you could have the applet communicate
with the server, and the applet could force a refres
Don't know if Jeff's interested in this much depth,
but adding to Nick's method ... :)
At 04:20 AM 1/15/2003, you wrote:
Adding to Justin's method, you can make this polling a more subtle event
by placing a polling jsp page in a frameset with your jsp page, but have
the polling page take up no
Nick,
I like this idea. Do you know of any examples that
make use of this concept? What code would I use
(generically) to have the invisible frame force a
resubmit on the viewable frame?
Have you ever worked with pushlets? Are they worth
messing with?
thanks,
-jeff
--- Nick Sophinos <[EMAIL PROT
Other alternatives which you should consider...
1) Deploy an applet that displays the information that you expect to
change. Then you can manage how often the applet checks for changes and
refreshes its own view. The implication is that your users will require to
have a JRE installed.
2) Dec
