>Hi Perry:
>
>Don't have any experience with WWWC, haven't been tasked to do any web development yet :( Just heard that others were saving information to object properties, then persisting them with OBJECTtoXML() as a means of maintaining state.
>
>Personally, I would tyr to avoid excessive round trips to the server and do the validation somehow in client side script. Also, ASP has session objects for storing variables and object references during a visitors session.

I don't see how that's relevant. If you have forms that lots of data you have to make trips back to the server, or alternately capture and store all of that data on the client. If you're talking about a pure HTML based web application, then the proper approach to complex forms is to do a Wizard like step by step approach to avoid excessive user interfaces.

As to ASP sessions and storing COM objects - this scales very badly (especially if you're using VFP or VB objects) and should be used only in low volume applications. The XML mechanism for storing data also works with ASP sessions and it doesn't dimininish the flexibility of any of that functionality.