Hi, The over all idea is really interesting and nice, but I think it is a hard one to implement correctly in the framework.
Having complete page state in GET requests (as context/parameters) may be troublesome for complex pages with a lot of state (there seem to be an URL size limit around 2000 chars). Using POST may be an option for some things or a totally different paradigm where state is kept server side and the key to locate the state is passed around could be possible... Even though the existing solutions with the server side state clearly has their own set of issues. The discussion is very interesting though ;) -- Chris On Wed, Mar 19, 2014 at 2:42 PM, Lance Java <lance.j...@googlemail.com>wrote: > Hi Geoff, I'm thinking this can also be done with the onevent mixin I > mentioned earlier. Since it can send a (configurable) list of clientside > field values to the serverside event, you can send all field values that > your event cares about. > > If two fields (eg select menus, text fields) determine the behaviour, send > both. >
