{"json_modified": "2016-03-28T08:14:47.733688", "uuid": "1fae5087-3bd6-4744-ae81-5567dfc9fbc8", "title": "XPCOM Thread Synchronization", "url": "/en-US/docs/Mozilla/Tech/XPCOM/Thread_synchronization", "tags": ["Thread_Synchronization", "XPCOM", "Threads"], "translations": [], "modified": "2015-07-17T01:23:43", "label": "XPCOM Thread Synchronization", "localization_tags": [], "locale": "en-US", "id": 16974, "last_edit": "2009-04-28T05:34:07", "summary": "XPCOM thread synchronization primitives have the same semantics as those in NSPR, and each method of these synchronization objects (e.g. Mutex::Lock()
) has a matching function in NSPR (PR_Lock()
). This is no accident, as mozilla:: primitives are merely bare-minimum wrappers around NSPR's.", "sections": [{"id": "Quick reference", "title": "Quick reference: Difference between nsAutoLock API and new API"}, {"id": "Old construction", "title": "Old construction"}, {"id": "New Construction", "title": "New Construction"}, {"id": "Old Usage", "title": "Old Usage"}, {"id": "New Usage", "title": "New Usage"}, {"id": "Mozilla Synchronization API reference", "title": "Mozilla Synchronization API reference"}], "slug": "Mozilla/Tech/XPCOM/Thread_synchronization", "review_tags": []}