On Nov 24, 9:44 am, Mike Orr <[email protected]> wrote:
>
> [...]
>
> I normally do use specific variable names. But that's impossible when
> you want to have a generic route that serves a variety of different
> purposes. You can't have two routes whose paths differ only by a
> variable name, because the variable name does not appear in the
> incoming URL, so there's no way for Routes to determine which route is
> wanted (and it would select the first matching route anyway).
That's a good point, which I missed above. Given the following routes,
the second one would never match (unless, of course, a regexp was
added to {id} and/or {name}).
/api/{resource_name}/{access_type}/{id}
/api/{resource_name}/{access_type}/{name}
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
