On Nov 24, 11:09 pm, Mike Orr <[email protected]> wrote:
> It seems like we should just fix Routes then.
Cool. I'd have raised a ticket myself but I'm new round here ;-)
> So what do people use their JSON, XML, YAML routemaps for?
> Just for display?
I wrote a client too ("path-to") which uses the metadata to navigate
the server's model with expressions like app.users["mike"].posts
["hello-world"].comments or app.blog_comments["mike", "hello-world]
which I needed to script a real-world application (a Java-based
trading app). I'm aware of a couple of other projects using it, one
to pull together a distributed app, another which consumes the json
format in the browser.
The path-to client thing has been done before I know, but previous
attempts (to my knowledge) have tended to rely on routing conventions
being followed strictly by the server and therefore (to my mind)
rather fragile. I would be making more noise about both
described_routes and path-to were it not for the frustrating wait for
a significant rewrite of the URI Template specification.
> I also added a couple tickets for a routemap pretty printer and
> "paster describe_routes".
Cool
> --
> Mike Orr <[email protected]>
Regards,
Mike
[email protected]
http://positiveincline.com
http://twitter.com/asplake
--
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.
