The export feature is nice for exporting and posting in a forum or such. Would be nice though for a xml or json based import/export that is able to set the selected items, not just the values.
I just suggested cookies as its a straight forward client-side data mechanism that without any additional packages is available from javascript. A way to store data and make it available from within the site. You could use google gears too, but that requires a client-side installation.
There isn't anything really wrong with using cookies. Cookies are nothing but a text-based data storage mechanism on the client-side. As long as their isn't any real personalized information in them, there isn't any harm in it.
Session variables, no idea why one would not use them as appropriate, for storing data that is present between page transitions (although there are some other mechanism for that too) but more importantly information that can be cached for the user while his session is active (normal defaults are 30 minutes under most APIs). They aren't really appropriate if you are doing a site, such as yours, that can be downloaded and run locally via just html files.
Quote:
Originally Posted by BrianG
I thought about doing something with cookies, but discarded it and decided to implement the export/import function instead. I intended it so users would configure their setup, export the values, save them to a text file on their computer, and then re-import them at a later time.
But TBH, I've never really liked using cookies. They have their uses I suppose, but I'd rather not use them, or use session variables when I can.
|