>Ugh.. definitions.. <g>
>
>Well, I had read your description where you asserted that each component in a stateless environment must be able to, in my words, survive on its own. Doesn't that also imply that it can pick up where it left off - whether you use tokens or some other method(s) to keep track of a transaction in progress?
>
>If so I'd want to say that MSMQ/Queued Components are, in so many words, stateless.
>
>Am I making sense or just plain confused? <g>

Sure you're making sense....sortof. ;-)

Yes MSMQ/Queued Components are stateless. And yes, statelessness is a requirement of disconnected components. But the converse is not true.

Logical Example
A dog is a mammal.
I am a mammal.
Am I a dog? No. (no comments from the peanut gallery).

Mammal and statelessness are base attributes. Am I making sense?