that's the fun part with cookies - you dont have to make them interact during form submittion - they are sent to the server on every request (even images, e.t.c. of course that also has pitfalls... and explains why most high traffic sites choose to server resources from a cookieless (sub)domain)!
On Fri, Apr 16, 2010 at 06:12, Yury Luneff <[email protected]> wrote: >> i've done something like this once (outside tapestry) using cookies to store >> the selections (which were basically the entity ids) - then added some js >> to make each checkbox checked if needed. > >> This keeps each page's selections fine. > >> Additionally, as soon as a page's checkboxes are all checked, i would >> detect that >> in js and show a link "Select all other entries" which would store a >> predifined value in >> the cookie (you could use the word "all", because users where allowed >> to filter my table, >> I used a predifined prefix and the filter data) > > OK. Say we might do something like that in tapestry (actually, > yesterday we've tried to do something like a ajax form submit whenever > checkbox is checked, but thats bad). Suppose it's easy to add info to > a cookie in onclick for a checkbox. How do I hook to form submission > so I can put info from cookies to form submission? I'm only starting > to see what Tapestry.js does so I don't quite have a clue about that. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
