Home/ Questions/Q 7666211
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T14:46:36+00:00

I realize this might not be a best fit for SO, so please tell

  • 0

I realize this might not be a best fit for SO, so please tell me where I should move/post this if that is the case.

My idea is after a user signs into the system, store the user preferences on the client in the form of cookies. If a user modifies said preferences, update the cookies. I need to do this because some of the preferences are client related and will need to be looked at via JavaScript.

I realize I’ll need the preferences stored on the server as well. Just wanting to know if pulling them down into cookies is a good idea. My app is primarily ajax driven so I’d like to pull the preferences down once and just store them. I don’t want to push them with each server request.

I’d like to avoid things like Local Storage so that I don’t have to worry about browsers as much. Cookies seem to be supported heavily by all browsers.

Anyone concur or have a better way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally cookies are a good idea, provided that you don’t have to store a lot of data. Just few things to keep in mind when using cookies to store stuff:

    • user can edit the preferences by hand so make sure you don’t have things like is_root=false without additional server side checks.

    • this can be annoying when user removes cookies and preferences are gone, I would go for a server side preferences storage mirrored to cookies so JavaScript can use them.

    Other possibility would be to serve dynamic JavaScript, with inlined preferences, instead of static files – you could serve JavaScript the same as you serve dynamic HTML, but then you have to be careful with caching.

    • 0