Larry,

>*snip*
>>They're really two different things.
>>
>>Statelessness deals with ensuring that your application runs in such a fashion that it is able to survive in a world where a connection between parts of your application are able to survive interruptions in those connections.
>>
>>If your application runs on a local area network and is able to survive random occurances of someone unplugging network wires and then plugging them back in without notice that your application could be considered stateless as it can survive. <g> And pick right back up where it left off. It seems to me to require the use of a lot of tokens that help manage the process.
>>
>
>Doug,
>I think this applies to DNA more than it applies to statelessness. The concept of disconnected is also an attribute of MSMQ/Queued Components. JMO.
>
>*snip*

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>