----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
When I used to use pure servlets, I thought it was a good practice to close() your
streams when done. Then I started using jhtml pages.....When close was called, I
thought the connection from the browser to server would be disconnected...hence, if
your <SERVLET> was in the middle of your page, the rest of the page would not be
seen....of course this is not the case..but it would have made more sense to me if it
was......I'm not saying it should have any affect on anything. I was asking what
people consider to be the best practice in terms of using flush(), close(), setting
out=null, w/JSSI,etc.....but I guess JSERV/JSSI is so well written....it doesn't
really matter. It hasn't failed me yet.....I have it running on one site that handles
20,000 searches/day.
David
> On Wed, 12 Jan 2000, David Morton wrote:
> > I have many jhtml pages w/<SERVLET> tags......when these servlets finish, I
> > used to have flush() & close()....it seems that close() doesn't really close the
> > output stream since the rest of the jhtml file is still utilized when
> > tested....are there any gotchas for using flush() and close() in combination
> > w/JSSI? Also, what is the recommended practice of using close(), flush(), and
> > possibly setting output stream vars to null in the context of JSSI?
>
> I think close() (of the output stream) is deliberately worked around so
> that it doesn't do anything when called in a servlet called by JSSI.
> Protection against badly written servlets.
>
> But why would you want to close() the stream, anyway? And why should this
> have an effect on JSSI reading the .jhtml file?
>
> Peter
>
> --
> URBAN Peter Mail: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
