AfflictionNetworks/jmustache
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More edits.

Browse Source
This commit is contained in:
Michael Bayne
2014-03-31 10:01:15 -07:00
parent a5a30fe5dc
commit 69c832a3ac
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -3
View File
@@ -482,9 +482,9 @@ JMustache is internally thread safe with the following caveats:
one another, they'll simply both resolve the variable instead of one resolving the variable and one another, they'll simply both resolve the variable instead of one resolving the variable and
the other using the cached resolution. the other using the cached resolution.
So the executive summary is: it is safe to share a `Mustache.Compiler` instance across threads to So the executive summary is: as long as all helper classes you supply are thread-safe, it is safe
compile templates, and if you pass immutable data to your templates when executing and any helper to share a `Mustache.Compiler` instance across threads to compile templates. If you pass immutable
classes you supply are thread-safe, then it is safe to share a `Template` instance across threads, data to your templates when executing, it is safe to share a `Template` instance across threads,
with multiple threads executing the template simultaneously. with multiple threads executing the template simultaneously.
Limitations Limitations