I realized my previous post was a bit outdated in my assumptions. I think Rails 4 is using the cookie storage as default for the session, so I realize the 4k limit applies to the session. My multi-user login app (Devise) was using memcache for session storage. So I believe just the session id is stored in the cookie. I think if you like Devise, using the memcache session storage is very easy to set up. I would probably go that route if I was in your shoes.
One other possible gotcha is that the flash content is stored in your session storage, so mayhaps that is pushing you over your 4k limit ? I’m really just guessing on that. Just one other thing you can check. On April 6, 2014 at 4:26:55 PM, Abiding Dude ([email protected]) wrote: I posted this on the Devise group also, maybe there's a workaround to avoid having to use the db as a store. At a later point I'll switch to memcache, but right now I'm not there with time to get familiar with it. Memcache def on the roadmap though. I tried Rails 3 about a year ago and am just now returning to Rails as main dish, and am finding version 4 to be really smooth, almost no surprises/gotchas. Quite a pleasurable workflow. -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
