On 19 nov. 2010, at 14:15, Fabien Potencier wrote:

> On 11/19/10 2:07 PM, Thomas Rabaix wrote:
>> Ok +1,
>> 
>> I like this idea : /{path}/toto =>  path = cms/custom/url
> 
> The change I propose is just about the syntax. Your example is already 
> supported by both symfony1 and Symfony2.
> 

What a good news! but how ? I never find a clean way to do so, I always create 
a custom Route object and tweak the match method.


> Fabien
> 
>> On 19 nov. 2010, at 10:45, Daniel Lohse wrote:
>> 
>>> +1
>>> 
>>> Sent from my iPhone4
>>> 
>>> On Nov 19, 2010, at 8:46 AM, Henrik Bjornskov<[email protected]>  wrote:
>>> 
>>>> +1
>>>> 
>>>> Makes sense to me and would make the routing even more powerful.
>>>> 
>>>> On 18 Nov., 23:20, Fabien Potencier<fabien.potenc...@symfony-
>>>> project.com>  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]
>>>> 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
>> 
> 
> -- 
> 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

Reply via email to