Refine DDMS versioning approach for multithreaded use cases
Description
(Imported from Google Code)
Suggested by Brendan Hofmann. See discussion thread for additional detail:
https://groups.google.com/forum/#!topic/ddmsence/-w15LUr1eT8
Activity
r977 HTMLizes the Thread Safety Power Tip.
r976 makes minor updates to the DDMSence website for the next release. Still need to convert the Power Tip Word doc into HTML and link from documentation.jsp.
r970 contains the important changes for thread safety. A diff of these changes can be viewed at:
https://code.google.com/p/ddmsence/source/detail?r=970
r971 adds a simple multithread test for ISMVocabulary.
r972 - 973 include some minor cosmetic code cleanup.
The attached JAR file contains a standard build of the changes, with no warranty. I'm going to leave it available to anyone who wishes to try it out for the next couple weeks before doing a formal release.
Updated website docs to denote DDMSReader as Unsafe.
Added a quick write-up of planned technical approach.
This approach seems more contained than originally anticipated, so actual development should not take too long.
Revised Schedule:
Update classes according to attached technical approach. (start tomorrow night, T 12/16)
Make an unstable JAR file available for external cursory testing for around 2 weeks (expected by F 12/19).
Proceed with regression testing / code coverage activities in the meantime.
Proceed with website Power Tip, JavaDoc, etc. in the meantime.
If no glaring issues are discovered in external tests by F 1/2/2015, proceed with new release (expected by S 1/4/2015).
Allot time for potential rapid point releases in January / February to address issues in the wild, especially if holiday season prevents much external testing.
(Original author: connextabh)
Glad to help, thanks for keeping us up to date on your progress!
