+1 for an extended syntax instead of routes.
Blog post about http://blog.2partsmagic.com/restful-uri-design/ which
discusses some schemes (about halfway down, with the title "Choosing a URI
schemes for resource hierarchies" (sic)).
One thing to think about is how to define the creation of new resources via
templates,
e.g. /person/new
where "new" would be a reserved word; the template would be POSTed when
filled.
About the /dogs issue:
it may be solved by having the query parameter at the pattern level instead
of at the parse_as_rest level:
patterns = [ ('/dogs[pet]', query=db.pet.kind=='dog') ]
pros/cons?
Denes
On Sunday, December 30, 2012 1:04:13 AM UTC-5, Massimo Di Pierro wrote:
>
> It could be possible via routes but it would be nice it the syntax were to
> allow it. I stopped developing it because I though instead of reinventing
> the wheel with this syntax we may want to support some standard. Is there
> any?
>>
>>
>>>
--
