4 ms·
Preface: I absolutely love Revel, and I hope to put something built on it into production very soon. That said, I'd be hesitant to bring up Revel's session as
by throwit1979 13y ago
Preface: I absolutely love Revel, and I hope to put something built on it into production very soon.
That said, I'd be hesitant to bring up Revel's session as a positive. It shoves everything into a cookie instead of using the cookie token as a key to a serverside data store. Not only are you limited to 4k of session-local storage, but you're sending the entire payload across the wire for every single request. This is absolutely stupid and needs to change. I'm sure Rob is boxed in by limited time, and this is not intended for production use yet, but holy god, it's by far the worst thing about the framework.
- akmiller 13y agoWell, how hard is it to just use their session store to store a guid of some type and use that key to store session data in redis or some other storage?
- throwit1979 13y agoThat's what I do, and it's easy enough, but that's not the point. Revel is trying to be a comprehensive "ready to go" framework - and as such, it has all these other features fairly well covered, but it's falling down, relatively speaking, in this one.
- mbell 13y agoThis is the same thing Rails does by default. I much prefer it to server side stores. What on earth are you keeping in the session that actually causes it to be a problem? If it's more than an auth token and a bit of flash scoped data, it may be time to rethink how your managing state.