> This is a really interesting point. I often talk to 
> application developers who want to do this kind of thing.
> 
> In my view, doing this is going against the grain of HTTP. It 
> is not a connected protocol. It is a stateless 
> request/response protocol.
> 
> When people start pretending that it's connected (as 
> application developers often want to do) the user interface 
> often ends up being quite klunky. Users do notice. But they 
> often don't complain about the actual problem (auto-polling 
> or whatever). But I find that when the central problem is 
> fixed they get happier.

        It's always seemed to me that very quick tasks are fine - 
        which is what most text book examples seem to be - but
        "real world" tasks quite often take a bit of time.

        I keep going down the same paths..

        Either I try to cache things on the server (Sessions or
ServletContext)
        - which can get very bloated in the case of in-memory XML
Documents
        which is what I use for my reporting (XML/XSLT) 

                OR
        
        I do some generate-once-server-many times at the HTML level but
the
        requests can all be for different date ranges/populations

                OR

        I avoid the above by doing dynamic queries - in which case
        I need to try to optimize everything* (Java, Tomcat config,
        XML structure, XSLT/Xpath structure, SQL/Stored Procs) to 
        make it fast AND tell the user to wait - which is where I
        started this thread.

        
        * - I realise that I should always be doing everything in the
        most efficient way - but I'm only human and can't just spew
        out "perfect" code - whatever that is.


> 
> Authentication is actually why I built my version of the 
> filter API which I later proposed to the Servlet team. 
> Authentication is the one good reason for having filters in the spec.

        Well it gets my vote - I tried all sorts of things for 
        authentication until I found Filters.  That was a happy
        day - well done!

___________________________________________________________________________
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

Reply via email to