Andy Spitzer wrote: > Woof! > > On Thu, 29 May 2008 16:32:35 -0400, <[EMAIL PROTECTED]> > wrote: >> main/sipXconfig/neoconf/src/org/sipfoundry/sipxconfig/sip/TransactionApplicationData.java >> > > If instead of using java.util.concurrent.Semaphore, check out > java.util.concurrent.SynchronousQueue. You could place the response > on that queue. That way the code that is blocking on > TransactionApplicationData object can instead poll() for and be > returned the actual ResponseEvent (or a TimeoutEvent) and act on it > (including the error cases that aren't currently handled) in the > correct thread context. > > --Woof!
Indeed using queue seems to be much more elegant way of doing that. I'll change it, unless Ranga will get there first of course :-) D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
