Update README.md
no change of content. Improved text
This commit is contained in:
		| @@ -11,13 +11,12 @@ tags: | |||||||
| --- | --- | ||||||
|  |  | ||||||
| ## Intent | ## Intent | ||||||
| Securing variables global to a thread, i.e. class variables if a Callable object,  | Securing variables global to a thread against being spoiled by other threads. That is needed if you use class variables or static variables in your Callable object or Runnable object that are not read-only. | ||||||
| against being spoiled by other threads using the same instance of the Callable object |  | ||||||
|  |  | ||||||
|  |  | ||||||
|  |  | ||||||
| ## Applicability | ## Applicability | ||||||
| Use the Thread Local Storage in any of the following situations | Use the Thread Local Storage in any of the following situations | ||||||
|  |  | ||||||
| * 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 class variables in your Callable / Runnalbe 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. | * when you use static variables in your Callable / Runnable object that are not read-only and more than one instances of the Callable / Runnalbe may run in parallel threads. | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user