quwiltw
Contributor
Some folks on my team want to change our data access layer to be all Shared methods instead of requiring new instances for single method calls. Would this not introduce the opportunity for problems in these methods? My understanding is that even the variables inside the implementations are shared so that if two clients made a call to a DAL method at the same time it introduces the potential for conflict. Am I wrong?
On a side note, I argue that a "stateless" class/component does *not* imply all shared/static, my colleague says it does. I say that as long as the class makes no attempt to maintain any state after the caller is done it can be called stateless. Who's right?
On a side note, I argue that a "stateless" class/component does *not* imply all shared/static, my colleague says it does. I say that as long as the class makes no attempt to maintain any state after the caller is done it can be called stateless. Who's right?