ThreadSafeCallHandler checked-in

Topics: Development Team Discussion, User Discussion
Coordinator
Aug 16, 2007 at 6:50 PM
http://www.codeplex.com/entlibcontrib/SourceControl/DownloadSourceCode.aspx?changeSetId=9297

However it is more for discussion purposes than anything else.

  1. I would love if you could comment regarding naming issues ( Contextual prefix )
  2. Unit tests are almost inexistant (Async stuff is hard to test!)
  3. I consider I had to re-write (read copy/paste) way too much stuff from Remoting interception as many classes were either internal or lacking relevant extension points

If you think that is not the way to go for thread safety, I'll just revert the change set.

Regarding the feature itself:

  1. There is no need to specify a SyncRoot if only one is to be present on an instance, an empty string is a valid name
  2. In order to have different methods on an instance use different sync roots, you should name their attribute syncRoot differently.
  3. If the attribute is placed on the class or a Type mathing rule is used, only one sync root will be used for the whole instance and all methods will be synchronized.

I'll come up with unit tests and samples in a bit.

Enjoy!