> From: Juozas Baliuka [mailto:[EMAIL PROTECTED]
> 
> > I don't close the session at all in any of my business logic
methods. In
> > deployment, a servlet filter _always_ closes the session at the end
of
> the
> 
>  It looks like not the good way for performance. As I understand
> "doFilter()" returns after output is sent and
> connection is open/locked too long ( waits for "out.flush()" ).
> I have never used Fillter to close connection in production (I close
it in
> "controler" or "dispatcher"), but this way is very simple, doe's it
> performs
> for you ?

The main advantage of using a filter is that it lets "live" objects
lazily populate during view rendering.  If you're worried about the time
it takes to write the output to the client, put Apache inbetween.  It
will act as a buffer and reduce the "occupation" of threads in your
appserver.

Jeff Schnitzer
[EMAIL PROTECTED]


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to