Howard Lewis Ship <hlship <at> gmail.com> writes: > > Yes, and persistent properties on the client help ensure that the > appllication state stays associated with the request not the session.
This will help tremendously for component writers. When this becomes available, why not make the built-in components such as Conditional and Foreach act like FormConditional (or MindBridge's IF) and ListEdit (or MindBridge's For)? It should be the component's job to ensure that its state doesn't change between render and rewind. The only issue I can see with this approach is that the source will have to be serializable if Foreach is going to kee the state unchanged. To solve this problem, this feature can be make optional at runtime by setting a parameter (just like in .NET people can enable or disable the "view state" for the data grid). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
