Raffael Luthiger wrote: > Thanks Gilles, Mark and Luke! > > I was thinking about the cookie as well. But the problem I see here that > a cookie can have in the maximum the size of 4k. It's not that I would > reach the limit now, but I don't want to run into strange problems as > soon as the application get larger over time. From this point of view > Mark's solutions is more flexible. And I can generate those hidden input > fields when I generate the page as well.
Use the cookie to set a unique id, the get the uid and do an ajax call to the server to get the larger state info from a database, based on the uid. -Steve > The idea with the classes can get a little bit messy since I already > have IDs and classes on those divs. > > At least I see that nobody would go for my favorite option. So I can > probably drop it. > > Raffael > > Webunity | Gilles van den Hoven wrote: >> Option 3, but save the data you got from the server in a cookie, which >> you destroy after 1 day or something like that. Each time the user >> changes the div, a new cookie is set and data is send back to the >> server. This saves you half in traffic and is the best solution if you >> ask me. > > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
