>>>When will this code break?
>>
>>If the object is cached by MTS or COM+, (like when using SetComplete or SetAbort) the actual object you get on the second call can (and probably will) be a different object.
>
>In Rick's example, how do you think he is getting away with using stateful objects?

Rick is programming with WWWC which has its own pool manager. IOW, he doesn't use a COM+ application for managing objects. I haven't seen the class he is describing in your link, but my guess is that it also supports stateless calls that describe the requested or submitted data with XML.