> * some people say, it's best practice to put 1 connection into 1
> user's http
> session and use it for all requests of that user
This should not be done because you end up having one
connection/session. Moreover connection objects are not serializable.
> * other people say it's best practice to use a connection for every
> request.
> (and if more than one methods are involved, the connection should be
> given
> as a method parameter)
This is safe, but resource hungry.
> * again other people argue that they don't care at all about reusing
> connection, they just open and close them when they need/want to
>
> who is right? or, how do you handle it?
This is also resource hungry.
The suggested approach is to setup Orion for connection pooling, and
get connections using the datasource as usual.
Subbu
=====
__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
