> * The default PHP paradigm is to have only one global scope, so people will > expect that their object stay the same whatever request/sub-request they are > in.
Isn't this expectation wrong? If people assume it is legit to transport state from a master request to a sub request using a shared service, they will have problems as soon they turn on caching (i.e. separate master requests). What's worse, these problems might not be apparent right away. I think it's better to have WTFs during development than during production. Bernhard -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
