-
Notifications
You must be signed in to change notification settings - Fork 152
October 16, 2019 #317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Introduce Server-Side Rendering ~ 15 min. |
Introduce stateless tokens #320 ~ 15 min |
Deprecate result factories in favor of one generic magento/magento2#24711 - 5min |
Server side rendering:
Stateless tokens:
Result factories:
|
Re stateless token: Generally I favor this approach. Regarding the 'user data being loaded anyway', I was suggesting to use a value here (like sequence number or nonce-like value) when constructing the token as a mechanism for revocation strategy. During decoding of the token, this value can be compared against what is in db for that user, and if it is same, token is valid. You can revoke a token by directly updating this value for a user. It is just one-possibility if a revocation mechanism is needed. Some pros and cons being mentioned here: https://phillbarber.blogspot.com/2014/02/client-side-vs-server-side-session.html (note: the article mentions using a public/private key pair, but it is not necessary for simpler setups). |
Uh oh!
There was an error while loading. Please reload this page.
Please add your topic as a comment to the issue. Use following format:
Topic description and link to PR, if any (duration in min)
Time: 10:30am CST/CDT
BlueJeans Meeting - https://bluejeans.com/7385677850
🎥 no recording available
The text was updated successfully, but these errors were encountered: