Woof! On Thu, 17 Sep 2009 12:33:12 -0400, M. Ranganathan <[email protected]> wrote:
> sipXrelay is not set up to deal with this form of re-entrancy. i.e. it > cannot deal with multiple outstanding requests from a single client. > However, that can be changed if needed. That would be the correct answer. Making assumptions about what the client will do is never a good idea. Someday another client may come along. Protect the server side, even with one honking "one request at a time" type mutex. Would the same problem occur if two different clients made a request at the same time? If so, there's obviously no locking the clients can do to synchronize with each other, so it's a server problem and needs to be addressed there. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
