Hi people-
I'm writing a simple little client/server thing in BEEP using two
profiles and I've run into a runtime issue with beepcore that I think
should be addressed. Perhaps I'm not understanding how to use the
startChannel method..
Basically, I end up firing up two threads and calling
startChannel on the session object (passed in to each thread). This
appears to yield a race condition where each thread ends up causing a
<MSG> to be sent on channel zero without a RPY being received and some
sort of deadlock, with apparently the second channel creation request
failing.
In short, startChannel doesn't seem to be threadsafe and I think
it absolutely should - not sure if this is a bug or an intentional design
choice.
I checked the sf site and did not see this as a reported bug or
issue, and I'm not sure what exactly it is (feature or bug).
-Gabe
--
Gabe Wachob gw...@wa...
Personal http://www.wachob.com
Founder, WiredObjects http://www.wiredobjects.com
|
