Allow use of local storages instead of cookies
Allow use of local storages instead of cookies
pigletto
Posts: 1Questions: 0Answers: 0
Currently it is only possible to save state of datatables by using cookies. This has a drawback of creating big requests that sometimes also tend to cause '400 Bad request' errors (because of size).
I think it would be nice to allow users to choose (by some settings) whether they want to use cookies (customizable lifetime), local storage (indefinite lifetime) or session storage (session lenght lifetime).
Of course there has to be some feature detection involved in order to support older browsers (possibly with fallback to cookie), but in general, this shouldn't be hard to implement.
I think it would be nice to allow users to choose (by some settings) whether they want to use cookies (customizable lifetime), local storage (indefinite lifetime) or session storage (session lenght lifetime).
Of course there has to be some feature detection involved in order to support older browsers (possibly with fallback to cookie), but in general, this shouldn't be hard to implement.
This discussion has been closed.
Replies
Thanks,
Allan
Any ideas when this feature will come? Due to the same problems as pigletto has/had I also need that. :-)
I think about implementing it for my own as a kind of hack, which means loading the data from local storage, pass it to a cookie so DT can use it and after the table is completely initialized delete the cookie data.
But I am not sure what drawbacks will arise when I implement so. Guess, pagination etc. good make trouble if the cookie is not there etc.
So, a timeframe for that feature would be great! :-)
Thanks a lot, Allan
Allan
As you might think, I am _very_ eager for beta 2 and the blog post now. even more than before. :-)
Thanks a lot, mate!