{"issue":{"created_at":"2011-09-25T17:14:59Z","state":"closed","updated_at":"2011-11-25T19:17:30Z","user":{"gravatar_id":"663594d46a2ebfe53ae26e7e14e56f51","id":939073,"url":"https://api.github.com/users/smillidge","login":"smillidge","avatar_url":"https://secure.gravatar.com/avatar/663594d46a2ebfe53ae26e7e14e56f51?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":2,"body":"The current draft of the spec is pretty vague on which classes are Thread safe. Can we add to the javadoc or the spec body in the Concurrency Effects section a definitive statement on each class whether it should be thread safe. The current Concurrency Effects section is more of a discussion rather than a definitive statement to guide implementers and users.\r\n\r\nJustification is, the first question any good dev is going to want to know is what is thread safe.","assignee":null,"id":1734210,"number":23,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Spec is vague on Thread Safety","closed_at":"2011-11-25T19:17:30Z","html_url":"https://github.com/jsr107/jsr107spec/issues/23","url":"https://api.github.com/repos/jsr107/jsr107spec/issues/23","milestone":null},"action":"created","comment":{"created_at":"2011-11-25T19:17:30Z","updated_at":"2011-11-25T19:17:30Z","user":{"gravatar_id":"6beae78fd4d033568534f4c1155623c8","id":225924,"url":"https://api.github.com/users/gregrluck","login":"gregrluck","avatar_url":"https://secure.gravatar.com/avatar/6beae78fd4d033568534f4c1155623c8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"We deleted the widely criticised section on Concurrency Effects. When we have something in the spec to say on concurrency (in the single VM case) or consistency (in the multiple VM case) we will do it in specific places. Thanks for the feedback.","id":2877360,"url":"https://api.github.com/repos/jsr107/jsr107spec/issues/comments/2877360"}}