I'm wondering for "one-off" simple settings (eg. preferredTextSize, chatSupportWindowMinimised, etc.) - not related to authentication - if there's any downsides to using Remix's Cookie API instead of Session API? While both options are documented and you can do whatever you want, there's this line stating: "While you may create these cookies manually, it is more common to use a session storage." - I'm asking "why" is it more common, what am I missing? (is it just a bit better DX?)
#Cookies (createCookie) vs CookieSession (createCookieSessionStorage)
1 messages · Page 1 of 1 (latest)
I usually use individual cookies for things not related to the user and the session for things related to the user or to the current session
e.g. I have a cookie for redirectTo, for promo codes, for csrf, invites, etc.
one benefit of sessions over cookies is that if you use another session mechanism your session will not have size limit