On Wed, 2010-01-06 at 13:59 -0500, Scott Lawrence wrote: > I think it's a bad idea because it makes the lock scope ambiguous. If > I've got a block with an OsLock at the top, I don't want it to be > possible that anywhere in that block is not holding the lock (the > reverse bug from the one that bit you).
That's a good point, though the problem isn't so much that "everywhere in the block is holding the lock" as "you can't get out of the block without releasing the lock". I'll have to think about this more. (But I'm checking it in for the time being so as to get the SipSubscribeClient fix going.) Dale _______________________________________________ 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/
