On Tue, 23 May 2000, Rickard [iso-8859-1] �berg wrote:
> BTW, speaking of overhead. In a EJB context the "last used" scheme that
> you had in the pools is quite overkill, since the usage is always short
> (hence a timestamp on getConnection is sufficient).
>
> So, at least for jBoss' purposes they could be simplified quite a bit in
> this regard.
True - except in the case of stateful session beans. In that
case, I think the user can control when to end the transaction (even
spanning several EJB invocations). So perhaps we could include a
parameter to disable last used updates - really, in a stateless or entity
bean, the last used time might as well be when the connection was checked
out of the pool. If you are not using a pool with stateful beans, you can
save the overhead.
Aaron
