On Saturday, March 15, 2003, at 05:53 PM, Nicola Ken Barozzi wrote:
Peter Royal wrote, On 15/03/2003 23.46:
I found a bug in the AbstractCompleteSocketStreamServer.
Peter, we should move these development mails to
[EMAIL PROTECTED]
It's not your fault, the documentation is lacking.
Didn't know t
On Saturday, March 15, 2003, at 05:55 PM, Paul Hammant wrote:
Ooooh, been looking for something like that. Marathon (
http://marathonman.sourceforge.net/ ) is being bugged by an issue that
sounds like it be caused by that.
Lets go for START & STOP. The intermediate states were just just
over-d
Peter,
Ooooh, been looking for something like that. Marathon (
http://marathonman.sourceforge.net/ ) is being bugged by an issue that
sounds like it be caused by that.
Lets go for START & STOP. The intermediate states were just just
over-design anyway.
Clearly a case of a missing or malfuncti
Peter Royal wrote, On 15/03/2003 23.46:
I found a bug in the AbstractCompleteSocketStreamServer.
Peter, we should move these development mails to
[EMAIL PROTECTED]
It's not your fault, the documentation is lacking.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba vol
I found a bug in the AbstractCompleteSocketStreamServer.
The code sets the internal state to STARTING, then fires off the thread
to monitor the socket, then sets the state to STARTED.
The thread that monitors the socket does its thing as long as the state
is STARTED. I'm seeing the monitor thre
