OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services
Jorge Williams shares some of the challenges and lessons learned while adding extensions to OpenStack.
Jorge Williams is a Principal Architect in the Rackspace Cloud Integration Team where he develops tools and services to solve integration problems. He has aided in the design and development of the Repose HTTP proxy, the Cloud Servers API, the OpenStack Compute and Identity APIs, and the OpenStack extension mechanism.
The World’s Largest Conference Dedicated to SOA, Cloud Computing & Service Technologies.
I am confused
Now, you are telling us that because "RESTful" services can't support namespaces, we have to create a central registry of some kind of contract metadata. You are telling that extensibility is really hard to reach.
To me, HTTP headers sound like an obscure non RESTful kludge for dealing with extensions.
Looks like you could have done all this work with WS-* in a fraction of the time. Am I mistaken?