Having a way in cornice to define resources sounds nice and useful, However, part of what you're doing with the code you submitted is already handled by what we've done in cornice (https://github.com/ mozilla-services/cornice/blob/master/cornice/service.py#L87) we could for instance deal with a Service class internally to define the routes and the appropriate callables.
I've done something similar for Flask in a flask-rest: https://github.com/ametaireau/flask-rest/blob/master/flask_rest.py, the definition looks like this: https://github.com/spiral-project/ihatemoney/blob/master/budget/api.py#L63 I went for get, list, add, update and delete as name of the methods because HTTP verbs carry some meaning with them (for instance, PUT does not means "update", but we can also stick to the http methods + list for the index. What do you think? -- 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.
