Gregory Polimis wrote:
>
> Question: Can I implement a "blocking" method on the servlet so it can
> wait for an indeterminate period before calling a method to write
> the results to the web-client?
>
As you noted, the problem isn't the servlet (which will
quite happily block for a very long time) but the client.
Off the top of my head:
1) If you have control over the deployment environment,
you might consider using an applet. Applets can be
a major pain to deploy, though. (There are more kinds
of web browsers than are dreamed of in your philosophy)
2) Have the servlet return a preliminary result that has
a refresh tag. Details in the archives, try searching
on "meta refresh".[1] Note that this one isn't guaranteed
to work across every browser, but chances are it will
work on the ones you care about.
#2 is probably the one you want.
-cks
[1] well, "meta refresh" should get you some good hits, but
the %&$#@ archive search is down (or so slow as to be
indistinguishable from down), so I can't confirm. Or just
try google.
___________________________________________________________________________
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
