...
Wiki Markup |
---|
While client-side locking is acceptable when the thread-safe class commits to its locking strategy and clearly documents itits locking strategy, Goetz and colleagues caution against its misuse \[[Goetz 2006|AA. Bibliography#Goetz 06]\]: |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ddb0b6e1e8c7cd3a-4ddfa8b6-4cc74f77-8b65bf66-12246b786a7c2d11c4c809b3"><ac:plain-text-body><![CDATA[ | [[API 2006 | AA. Bibliography#API 06]] | Class Vector, Class WeakReference, Class ConcurrentHashMap<K,V> | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3b9918851531bbb4-7b1f5020-4f6a452e-ac1cb82d-0244dfe44d60cad565af037d"><ac:plain-text-body><![CDATA[ | [[JavaThreads 2004 | AA. Bibliography#JavaThreads 04]] | 8.2 "Synchronization and Collection Classes" | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5f957d6f81996752-c47a2e89-4c974c87-be528655-169e444ec756322ed14a4b33"><ac:plain-text-body><![CDATA[ | [[Goetz 2006 | AA. Bibliography#Goetz 06]] | 4.4.1. Client-side Locking, 4.4.2. Composition and 5.2.1. ConcurrentHashMap | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="022912d7d0b3004e-c2a4e30a-48e24a93-a2f5b3fa-dca54b5bbbb5493016f431f1"><ac:plain-text-body><![CDATA[ | [[Lee 2009 | AA. Bibliography#Lee 09]] | "Map & Compound Operation" | ]]></ac:plain-text-body></ac:structured-macro> |
...