how hard would this really be? we simply store the IPageMap entry in a
serialized hidden form field and put it back in the pagemap on request
handling. am i missing something?
Jonathan Locke wrote:
so we do have stateless pages and we do have IPageMapEntry.
two things:
1. what does the code look like to encode/decode params for a
stateless page into url?
2. now that we have IPageMapEntry, it could make more sense to allow
page state serialization! rather than serializing the whole component
tree, you can tune the state sent back to the browser to just the
state needed to reconstruct the tree (The IPageMapEntry object...
which would only be the Page in the worst case where the user does not
care about bandwidth). seems like this combination of techniques
could be a silver bullet for many who want stateless pages. thoughts?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
