The effect of the current isClosed() method is, that disconnect is never detected and that might be unwanted in some situations.
What kind of situation do you mean?
I could imagine a situation, where the currect behaviour might not be very clever:
If you write a pool, that checks every connection in the pool, if it has timed-out, or if it is already closed.
If there is any ConnectionPool implementation out there, this will cause unwanted connects to the DB-Kernel. I currently have such an implementation, but in fact i did until i "optimized" my pool a little.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
