Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for clarification of Thread Safety. #4

Open
GoogleCodeExporter opened this issue Apr 22, 2015 · 0 comments
Open

Allow for clarification of Thread Safety. #4

GoogleCodeExporter opened this issue Apr 22, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

For thread safe components, I like to document the type of thread safety. 
This information could be checked staticly.
e.g.
- The caller is responsible for thread safety. This could check the caller
actually does this is some way. e.g. has a ThreadSafety annotation.
- Locking is global by a static lock.
- Locking allows one thread at a time per instance
- Locking allows concurrent read (one thread writing)
- Locking allows concurrent reading and writing.
- State is thread local.
- The class/object is stateless.
- The thread safety cannot be determined staticly.

Currently, there is only two annotations ThreadSafe and NotThreadSafe with
no distiction, or checking of the type of thread safety.

Original issue reported on code.google.com by [email protected] on 27 Jan 2009 at 5:01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant