In fact the JDBC provides anyway to handle this in `Statement.cancel()'
which allows an executed SQL query or update to be halted from _another_
thread. In other words the CancellableThread or equivalance is the
responsibility of the JDBC driver implementor not the JDBC user. Careful
programming with state transitions should alleviate any headaches ...
Pete
______________________________ Reply Separator _________________________________
Subject: Re: Deprecated `Thread.stop()' in forthcoming JDK 1.2. Wh
Author: trebla ([EMAIL PROTECTED]) at lon-mime
Date: 22/11/98 19:32
Steve Byrne <[EMAIL PROTECTED]> writes:
> This, in effect, is that the interrupt mechanism does. It sets an
> interrupted flag in the thread that user code can watch for, and I
> think it breaks you out of Thread.sleep or other thread related
> operations.
Right. Sleeping and blocking I/O are interrupted by the interrupt
mechanism; when this happens, the I/O methods and the sleep method
throw an appropriate exception that tells you it is interrupted.
I want to remark that there is no silver bullet; so I am glad that a
silver bullet is deprecated.
