Thanks for your post. Troubleshooting synchronization is the same as troubleshooting a proper method in that you can use the call graph to find all of the methods that fed into that. For instance, thread.Abort, WaitHandle.WaitOne, and other synchronization methods will contribute to this.
I would assume that this is just because web applications are sending data out on different threads and setting up wait-states that end when all of the data has been sent or recieved, so it may or may not be important.
Comments
I would assume that this is just because web applications are sending data out on different threads and setting up wait-states that end when all of the data has been sent or recieved, so it may or may not be important.