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 app
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
I'd go for something like option 4, but instead of the custom attribute/DTD
stuff, just give it
a classname. i.e.:
Luke
Raffael Luthiger wrote:
> Hi,
>
> I've seen searching lately for a good way of storing preferences which a
> jQuery script needs later on. The specific information the scr
Raffael Luthiger wrote:
> 2) The js-script gets generated each time the page is called. And the
> corresponding vars are set in there.
>
> 3) Every time the page is loaded the js-script asks the server for a XML
> (or JSON) file with the preferences in there.
>
> 5) More (and better) ideas?
I'
Raffael Luthiger wrote:
> 3) Every time the page is loaded the js-script asks the server for a XML
> (or JSON) file with the preferences in there.
>
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
change
