maybe my question is stupid, but I really need to know
when an Object is to be considered "stateless".
I see everywhere that Object to be pooled and to be avtivated JIT must be stateless, but what does it mean exaclty?
I read that an Object to be stateless should have no attributes, but this means that it's not an Object but a set of functions ... this means that I could throw away all the OOP concepts ... and I don't like this idea.
I also read (but I hope this is not real) that code like this:
Set X = CreateObject("MyObj")
X.MethodA(); 'This method sets the value of attribute "A"
... other stuff
Y = X.A;
should not work because JIT and POOLING should give object
X to other clients that may change the object so when I read attribute A of X (if X is a transaction Object in MTS) I could not get it as I previuosly set ... this seems to be orrible!!!
(I used VB syntax, but I'm interested in MTS concepts ... I know VB limits about pooling, in fact I will use C#)
Thanks for any explanations you have for me.