> > If I wanted to avoid the user have to keep clicking, I
> suppose could
> > put an auto-refresh header thingy in the busy page HTML.
> (Good or bad
> > idea?)
>
> Bad idea (mostly).
Hmmm. Thought so. I have an auto-refreshing page
showing the state of my (Quartz) Job queue. Never been
totally happy with it - and too many browsers left on
that page just bombard the server.
Still a bit reluctant to make the user do perform the
polling though. I guess I could add some form of "percentage
done" field to the Map held in the Session - then at least
they would see something was happening.
> > Lastly, is there something more generic I could do using Filters?
> > Ideally I'd like to set up a "BusyFilter" that maps to the
> URL pattern
> >
> > /servlet/apps/*
> >
> > Ideally this would display a busy page for any /servlet/apps...
> > request and require coding only in one place.
>
> Yes. You could implement the same pattern using filters. But
> filters are very complicated things and hard to get right (in
> retrospect I feel they were a mistake to include in the API).
>
> It would be easier to code the pattern as a helper class
> which you could easily use in your servlets that want this.
> Maybe extend HttpServlet if that takes your fancy.
Fair enough. I've not really used helper classes, but I
have written a couple of Filters for enforcing user
login/roles and they seemed to be worth considering.
Thanks again for your time Nic.
Chris
___________________________________________________________________________
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
