I don't think its short-sighted, in fact I use this approach, and it fits very nicely with traversal.
Having a static versioned API is not a necessity. You only break the (RESTful) API when you remove members from your resources. If you plan to do this you can always warn your clients in time. Big APIs on the web also change regularly, this is what (continuous) integration testing is for. This is all assuming you have consumers that you do not have a direct relationship with yourself. If you manage them yourself it is not even a necessary to delay your upgrade. -- 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.
