In order to continue the efforts of #335411, we aim to break the complex issue into more digestible parts.
Step 1: We contribute an implementation of Symfony's Session object to core but don't include any code that uses it.
#1858196: [meta] Leverage Symfony Session components
Step 2: This issue
We implement the basics of Session management using Symfony's Session Object.
Step 3: We implement complex topics
Lazy Loading (should be automatically provided by Symfony's Session but extra work may be required)
Secure Sessions (as of yet, an unsolved problem)
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 1858198_4.patch | 2.92 KB | cosmicdreams |
| #4 | 1858198_4.patch | 459 bytes | cosmicdreams |
Comments
Comment #1
cosmicdreams commentedThis issue is not longer postponed because #1858196: [meta] Leverage Symfony Session components is RTBC'ed. Now that we have a reliable method for registering the Session onto the DI, we need to use it to stub out a proper use of Symfony's Session object.
Comment #2
cosmicdreams commentedComment #3
cosmicdreams commentedI believe that the current focus is to use examples such as the one found at http://symfony.com/doc/master/components/http_foundation/sessions.html
Comment #4
cosmicdreams commentedHere's a patch that relies on #1858196: [meta] Leverage Symfony Session components being committed. It adds the SessionListener.php EventListener and registers it onto the DI. The patch doesn't work as sessions aren't started. But it's my current work-in-progress.
Comment #5
cosmicdreams commentedI meant to upload this patch.
Comment #6
Crell commentedComment #7
cosmicdreams commentedCrell, It's not ready to be tested yet. That the patch goes green is not a sign of it's readiness.
Comment #8
ParisLiakos commentedthis already works in the latest patch @ #1858196: [meta] Leverage Symfony Session components