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

Yet more edits.

Browse Source
This commit is contained in:
Michael Bayne
2014-03-31 10:02:15 -07:00
parent 69c832a3ac
commit 3c0c0f5b4a
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -482,10 +482,10 @@ 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: as long as all helper classes you supply are thread-safe, it is safe So the executive summary is: as long as all helper classes you supply are thread-safe (or you use
to share a `Mustache.Compiler` instance across threads to compile templates. If you pass immutable the defaults), it is safe to share a `Mustache.Compiler` instance across threads to compile
data to your templates when executing, it is safe to share a `Template` instance across threads, templates. If you pass immutable data to your templates when executing, it is safe to have multiple
with multiple threads executing the template simultaneously. threads simultaneously execute a single `Template` instance.
Limitations Limitations
=========== ===========