>
>PMFJI. Think of designing your classes with absolutely no custom properties, and you'll start seeing what additional parameters you need for your methods. That will buy you stateless objects.
>Just my .02

I'm not quite sure I follow. Are you saying to use this just as a design aid (if so, I think I understand where you're coming from)? If not, let me just add that there isn't anything inherently wrong with using properties - using them doesn't preclude a stateless design. You just can't depend that they will contain the same values the next time you need to use the object.