LS,
It has come to our attention that in the beepcore-java code the client
starting a channel can send a close but not receive one. This can lead
to null pointer exceptions when the server closes the channel
The way around this is to register a channel listener and look in events
whether this event concerns its own channel.
Wouldn't it be more efficient to make clients register a listener as
they request a channel? This listener would only gets events for its own
channel.
And shouldn't a client be encouraged to register such a listener by the api?
--
<insert value="your favorite astute quote" id="sigquote" />
-----------------------------
Daan Hoogland
software architect
-----------------------------
daa...@lu...
0620442544
www.luminis.nl
-----------------------------
<or ref="sigquote" />
|