Aaron,
Now you got it ;-)
OK, blocking by default is OK for me.
Who is resposible for the docu? He/she should update these then too and
explicitly point to the problems that may occur on blocking = false.
bye Daniel
On Sun, 08 Oct 2000, you wrote:
> Oh - wait. You were *suggesting we add that*. The light goes on.
>
> Okay, well, better to just turn blocking on. The point of
> blocking is to block, and the underlying pool already handles that. The
> point of not blocking is to allow the "client" to gracefully abort if the
> resource is not available. So you could display a "resource
> unavailable; please try again later" message or whatever. This is
> admittedly not what you usually want to do in an EJB, so we can turn
> blocking on by default. But if for some reason you *do* want to do it, we
> should not defeat it in the data source, we should let it happen.
> So I'll change blocking to default to on, and then if someone
> wants it to not block, they can change that easily.
>
> Aaron
>
