Update README.md
Some additonal description, deleted wrong pumlid
This commit is contained in:
		| @@ -3,7 +3,7 @@ layout: pattern | ||||
| title: Thread Local Storage | ||||
| folder: tls | ||||
| permalink: /patterns/tls/ | ||||
| pumlid: 5Sd13OGm30NHLg00uZlTc62HeCI9x6-s_ONJF6dMghd5AM5jAS3qdSZubwwA4aUuM1uAKQGyEg6CpZxSwUQ7jrEyNhfD1iJKwNql2Cr9aB-ci9vczFO7 | ||||
| pumlid:  | ||||
| categories: Concurrency | ||||
| tags: | ||||
|  - Java | ||||
| @@ -11,12 +11,13 @@ tags: | ||||
| --- | ||||
|  | ||||
| ## Intent | ||||
| Securing variables global to a thread, i.e. class variables of the Runnable object,  | ||||
| against being spoiled by other threads using the same instance of the Runnable object | ||||
| Securing variables global to a thread, i.e. class variables if a Callable object,  | ||||
| against being spoiled by other threads using the same instance of the Callable object | ||||
|  | ||||
|  | ||||
|  | ||||
| ## Applicability | ||||
| Use the Thread Local Storage in any of the following situations | ||||
|  | ||||
| * when you use class variables in your Runnable Object that are not read-only | ||||
| * when you use class variables in your Callable Object that are not read-only and you use the same Callable instance in more than one thread running in parallel | ||||
| * when you use static variables in your Callable Object that are not read-only and more than one instances of the Callable may run in parallel threads. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user