http - web application, best way to handle state -
i have crud pages have store state information, current page, records per page, current order, filter conditions, , way more information...
i'd use friendly urls similar rest style, http://microformats.org/wiki/rest/urls (get browsing, post add, put edit, delete remove)
the problem cookies if open several tabs, of them share same cookies, it's same session because session id stored in cookie
if try keep params in url (something /clients?page=1&len=10&sort=name&filter=smith) issue post loose values
the other solution store state on hidden inputs, , issue posts carrying around hidden inputs, in case can't use queries...
so, how handle web presentation state???
--
added:
to more specific
i have crud page, user can filter, change page, page length, , sort order..
after issuing update or insert, how can retrieve former page, page length, sort order, criteria filters (that presentation logic state), etc... taking account if user opens tab both tabs work same cookies...
the solution can think of use hidden fields...
you'd have both of suggestions, think.
whenever generate page server-side, make sure of forms on page have params hidden values, , links have params in url...
Comments
Post a Comment