On Jan 14, 2008 9:52 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> I've finished my Routes 2 spec.
>
> http://wiki.pylonshq.com/display/routes/Routes+2+Spec
>
> It defines a minimum functional spec, and optional features that can
> be added. This is to guide the
> implementation to make sure the core is robust. It also allows us to
> decide which features to support.
>
1. Mapper.connect('foobar') looks both simpler and more explicit than
RouteMap.foobar. Why this "magic"?
2. url_for -object certainly ain't simpler or more explicit either. Again, I
don't see how url_for().foobar is better then url_for("foobar").
3. "Unnamed routes will no longer be allowed". I remember Ben saying this
will never happen.
4. Redirect routes is a welcome addition. I'd like to help on this, if this
can help you to make it into "permanent" feature. ;)
5. Failure routes can be seen as a special case of redirect routes. E.g.:
m.redirect("employees/that_loser", None, 410). Or may be both redirect
routes and failure routes can be generalized to some mod-rewrite-like
feature.
6. url_for.current() sounds useful
Max.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
