>>mark,
>>
>>>>... until the boss says, now let's put this on the web.
>>>
>>>Then you get WebConnect. :)
>>
>>Yes, and you then run head-first into issues of stateless design. For simple queries it's easy to build something, but get into multiple input/editing screens, with the validation needs they bring, and you see the wisdom of not having to rewrite all of that code again.
>
>David,
>
>Is there some connection between "stateless code" and n-tier that I am missing. I certainly have never equated n-tier with 'stateless' in any way, shape or form.
>Just trying to learn of yet more stuff I've likely missed.
>
>Cheers,
>
>JimN

Jim,
PMFJI, but stateless is a concept of web-based and MTS/COM+ development. N-tier by itself does not necessarily make you take a stateless approach.

If you create an object, set some properties and run a method of that object that queries those properties for information, that is an example of "stateful" programming. You are expecting the object to remain in a certain state during its existence.

Stateless programming involves passing all the information needed for a given task to an object and then have it perform the task. It doesn't need to know anything outside of what you passed to work.

HTH.