Sorry, but there is an obvious solution that is more explicit: Use two routes!
On Fri, 25 Feb 2011 12:30:11 -0600 ryan weaver <[email protected]> wrote: > If you think you have a good handle on it and want to work on it, then I say > try it out. Two words of direction: > > * the feature cannot affect or obfuscate the currently functionality. In > documentation, it would be explained as an extra, advanced thing to do. > > * you must have good test cases in the work > > If anyone can think of why this is a bad or unnecessary idea, speak up. I > tend to think most ideas are good... to a fault :) > > @weaverryan > On Feb 25, 2011 12:22 PM, <[email protected]> wrote: > > -- > 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 -- 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
