Mike Orr wrote:
>> This won't be the same as url_for, which is tied to Routes, but ideally
>> it would have some API overlap. I haven't really thought about what it
>> would look like.
>
> url_for could be implemented on top of something. Of course there's
> always the need to parse and assemble URLs, which can be put in a
> class. What we're considering is an object with route-generation
> methods:
>
> url_for.home() # A named route.
> url_for.blog(id=1234) # Another named route.
> url_for(controller="foo", action="dig")
> # Use the default route (:controller/:action/:id)
> url_for.current(page=2) # Derive a URL from the current page.
> url_for.current("faq/") # Possibly a urljoin from the current page.
Hmm... I don't think WebOb could do anything that looks like this. If I
add something to WebOb I think it's going to look pretty different, so
no need to try to keep them similar.
--
Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
