Craig McClanahan wrote:
Let's try to be a bit more helpful here :-).
No object :)
The only thing Struts itself might do is try to set the no-cache headers if you have them configured. It does not, by itself, ever write to the response stream or response print writer. That's the responsibility of whatever your action forwards to.
Right, that's what I thought, thanks for confirming it!
Calling flush() doesn't necessarily cause the *entire* response to be sent, because you might still be creating more output. But it *does* cause the HTTP headers, and any output content you've written to be transmitted. From the perspective of the servlet API, this response has now been "committed" so you cannot later decide to do a redirect or forward. In general, the only use case I can think of for calling flush() yourself is if you have something like a "Request In Progress - Please Wait" at the beginning of your page, and you want that to show to the user while a time-consuming process is performed to create the remainder of the content.
Interesting... I would have thought just the opposite, but this makes sense. I suppose one could imagine a problem with a filter that does some post-processing occurring if you flush() yourself.
So, leave flushing to the next guy, contrary to what everyday etiquette would seem to indicate ;) LOL
Struts doesn't but the servlet container will, once your processing has finished.
This is a guarantee of the servlet API I would assume? It seems like it logically would be, but I wasn't sure.
Craig
Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
