> I do think client headers instead of urls have some pragmatic > approach here that is very attractive. Will definitely need a good > chunk of plumbing to support that in a sane way in the tree that > keeps the overhead from a review perspective low.
Aside from some helper functions to make this consistent, and some things to say "here's the code I want to return, but compat clients need /this/ code", I think this actually gets us most of the way there: http://paste.openstack.org/show/70310/ (super hacky not-working fast-as-I-could-type prototype, of course) Some care to the protocol we use, versioning rules, etc is definitely required. But plumbing-wise, I think it's actually not so bad. With the above, I think we could stop doing new extensions for every tweak right now. Of course, cleaning up the internals of v2 to be more like v3 now is a separate effort, which is non-trivial and important. However, v3 started as a copy of v2, so we should know exactly what that takes. --Dan _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
