I don't think performance would be changed as routing configuration gets cached.
On Tue, Nov 23, 2010 at 2:30 PM, Greg Militello <[email protected]> wrote: > I think that the argument of the colon having no intrinsic value can also > apply to this new method. So ultimately, given that the colon has no > meaning in PHP it comes down to what system for implementation offers > Symfony the most in return (be it functionality, readability, parse-ability, > speed, etc). > > Ultimately both of these systems seem to require a similar amount > difficulty for the developer, so that seems to be an non-issue. > > I think both systems provide vary understandable routing. > > It would seem the URI template could be slightly slower when we start > introducing things like default values, or other complex pattern matching > rules like in the RFC. Also, I would imagine a slight increase on basic > routing due to having to deal with two characters per definition. > > Ultimately, if the new URI routing system could be implemented without a > drastic speed drop, and if we can make it over-ridable (allowing developers > to extend the system to include things like default dates, or other logical > manipulations) I think this could be fantastic. Also, if it is extendable, > there would be nothing to stop someone from using the old colon format. > > On Nov 18, 2010, at 5:20 PM, Fabien Potencier wrote: > > > The current implementation of the routing uses a colon (':') as a > delimiter for placeholders in patterns: > > > > /article/:id > > > > This convention was already used in symfony1 and comes from the Ruby > world (where :something has a meaning.) > > > > But, :something has no special meaning in PHP and so, this is just a > convention. > > > > I propose to use the "URI template" notation instead: > > > > http://code.google.com/p/uri-templates/ > > http://tools.ietf.org/html/draft-gregorio-uritemplate-04 > > > > The above example would be written like this: > > > > /article/{id} > > > > It does not make sense to implement the whole specification in our > context, and so I'm just proposing to use the same conventions described in > the specification. > > > > For instance, we can probably also implement the default value: > > > > /article/{id=1} > > > > Fabien > > > > -- > > Fabien Potencier > > Sensio CEO - symfony lead developer > > sensiolabs.com | symfony-project.org | fabien.potencier.org > > Tél: +33 1 40 99 80 80 > > > > -- > > 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]<symfony-devs%[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]<symfony-devs%[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
