Ok this is more that you predefine where what should go. That looks like a nice coding strategy on itself that on decode time it maps the first param value to userid param and the second (profile) is used to get to the right mount class. At encode time it expects to find a userid param and adds the mount param also
On 2/8/08, John Krasnay <[EMAIL PROTECTED]> wrote: > On Fri, Feb 08, 2008 at 11:42:46AM +0100, Gerolf Seitz wrote: > > > > i have a working implementation for the above mentioned use cases, but i > > certainly wanted to get > > some opinions whether we want to integrate this. so i appreciate any > > feedback. > > > > cheers, > > Gerolf > > I think this would be really cool. > > One variation on this theme would be to give the parameters names a la > URI Templates (http://bitworking.org/projects/URI-Templates/). For > example: > > /user/{userId}/profile > > ...would result in a page with the page parameter userId set to whatever > was matched by {userId}. I think RoR uses something like this. > > jk >
