On 05/07/2012 06:01 PM, Bill Seitz wrote:
I agree, the human-UI needs to be optimized for an elegant UX, the API
needs to be kept logically simple.
For the API, you should be able to automate a lot of the CRUD
renderings by introspection on your db structure, equivalent to how
Rails/Django auto-generate an admin interface.
For more details, I suggest you read RESTful Web Services.
http://webseitz.fluxent.com/wiki/RestfulWebServices
What you say about elegance is true, but this should be a RESTful
system. Meaning, we're dealing with resources, not action URLs. An edit
page interface is just resource data wrapped in stylized form HTML.
Basically HATEOAS on steroids, so to speak. So there is no API in a
strict sense, just resources. A machine does not need stylesheets,
menus, sidebar content, so the machine uses plain JSON format. Human
might prefer fancy HTML format of teh same data, and more.
.oO V Oo.
--
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.
