You are right, but if your developing Thread-safe objects then you are problably already implementing (A)synchronous objects associated with them, so why even worry about Static(Shared) parts of an object?
In my past, if you are threading, then stay away from Static/Shared objects. I personally stay away from programming thread applications but that is just me. On Jul 12, 1:41 pm, "C." <[email protected]> wrote: > Hello, > > I have always made CRUD methods on my Business Objects static. > However, after going through the MS cert training kit 70-515, I came > across this: > > "if the business layer uses static methods (or shared methods, in > Visual Basic), the ObjectDataSource can use these > methods without creating an instance of the actual business object. In > this case, however, keep > in mind that you could end up with performance issues related to > thread contention as multiple > requests try to access the same static method." > > This passage would seem to suggest that each thread can only enter a > static method one at a time. If so, wouldn't this cause scalability > issues if a static method is used frequently in an application? > > I had never heard this, any explanation would be appeciated! > > Chris -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
