On Feb 2, 2011, at 6:56 PM, Mike Schrag wrote: >> How can we identify non-threadsafe classes without waiting for an exception >> or data error? > > you can't, really ... i would say that the majority of classes probably > AREN'T thread-safe and work your way back as you prove otherwise.
That is my take on it as well. An easier approach is to look at what you are sharing from the Application or static variables and focus on checking those classes. You might get better results by eliminating the sharing rather than synchronizing. Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
