In play, the word "client-side session" seems to mean that all datas are stored in a cookie in the client during session. And PHP, which is known to use "server-side session" , I think it is possible to store all datas in the cookie. Probably the difference is whether the cookie is singed with a secret key or not, but I am not sure. In a normal session known as "server-side session", you can set a cookie which has a session ID and then the server should deal with the session ID and can find the related specified values. In this session, the client has only the session ID, which is just a long number. And specified datas are stored in the server-side, so I assume it is called "server-side session".
I know in Play this approach is also possible, which means the client has the session ID and the server has some specified datas normally in the cache. At the same time, Play enables pushing all datas into the client's cookie, signed with a secret key, and my question is under what types of implements should we use the "client-side session"? I don't imagine and an official document about Play's session doesn't mention so deeply.
What is the use case? When do you implement the client-side session? Any comment or answer should be highly appreciated.
--
You received this message because you are subscribed to the Google Groups "Play Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framework+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/c5a978b0-f87f-4af7-ab63-535d9c8b5dc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.