mirror of
https://github.com/unicode-org/icu.git
synced 2025-04-05 05:25:34 +00:00
Documentation update
X-Trac-URL: https://ssl.icu-project.org/trac/ticket/72 git-svn-id: http://source.icu-project.org/repos/icu/icu/trunk@136 0a8b766c-62c9-45f9-954d-7f2943c9ead0
This commit is contained in:
parent
a14a570663
commit
277c983adf
1 changed files with 12 additions and 0 deletions
|
@ -57,6 +57,18 @@ necessary, however time spent inside the mutex is then minimized. </p>
|
|||
<p>Developers implementing the Mutex are not required to provide reentrant-safe
|
||||
implementations. </p>
|
||||
|
||||
<h3>Using collators in multi-threaded environment</h3>
|
||||
|
||||
<p>Instances of Collator class are meant to be used on per thread basis. Although it is
|
||||
possible to have multiple threads access one Collator there is no guarante that such a
|
||||
construct will work, especially if number of threads grows over 10. There are no
|
||||
limitations on number of threads if each thread creates its own separate instance of
|
||||
Collator class.</p>
|
||||
|
||||
<p>Test results have shown that case with 50 threads accessing 1 collator fails with a
|
||||
crash after 20 threads are reached. However, a test with 50 threads creating separate
|
||||
instances works well.</p>
|
||||
|
||||
<h3>Implementations</h3>
|
||||
|
||||
<p>On Win32 platforms, a reentrant mutex is most naturally implemented on top of a
|
||||
|
|
Loading…
Add table
Reference in a new issue