RailsConf 2017: A Deep Dive Into Sessions by Justin Weiss

RailsConf 2017: A Deep Dive Into Sessions by Justin Weiss

What if your Rails app couldn’t tell who was visiting it? If you had no idea that the same person requested two different pages? If all the data you stored vanished as soon as you returned a response? The session is the perfect place to put this kind of data.

But sessions can be a little magical. What is a session? How does Rails know to show the right data to the right person? And how do you decide where you keep your session data?

[kenmcf]

I love the pace of how he speaks...nice and quick.

[victormartins-software]

This presentation is gold. You really went deep, thank you, great example.

[upstill]

This is a great example of an information resource that gathers a heap of disparate information in pursuit of one particular problem (domain). The clouds in my head about sessions are dispersed! Now to fix the problem...

[sunnydivino]

There's something about Justin´s speech that make me go from "I hate rails" to "I can´t wait to build a new rails app"

[manojmj]

This will go down as one of my favourite RailsConf talks of all times! Super informative.

[GoranColovic]

Nice presentation. Would be cool to mention that CSRF is still possible. Would need to add some sort of X-CSRF-TOKEN in the header to protect against those attacks.