"I understand these benefits to this design: ""In a big organization, web traffic may be distributed across many servers, in which case the session information needs to be distributed, too. Flask's technique of putting session data in the cookie avoids this problem.




reading session files from disk: the data comes in with the request, so it's already in memory!

have session files accumulate on the server

moving sessions from one server to another (say for load-balancing): the session is in the cookie, so it doesn't matter what server responds to the request.deleting old, abandoned session files from the server""

But, also isn't it better for things to be in distributed systems though? When the info is distributed it is more fault tolerant with less reliance on one single server, so info can be recovered and retrieved, right? Or in this case we might be very reliant on the cookie itself?"

This might be out of scope of the class, but what are some ways to minimize session hijacking?

Clarifying the difference between Flask sessions and PHP sessions

I am still a little confused about how you're pulling data from the cookies could you elabrote about the session_cart() method.

Why is session data stored client-side in cookies rather than server-side?

Can we implement logout feature using Flask sessions?

None, I think I just need practice!