After many interesting conversations with jaypipes and cdent the last couple of weeks, and a few edge case API change patches in Nova, I decided to try to jump in and help provide context and an outline for the http guidelines in the spec.
This is a standard that's clocking in on 20 years, there is a lot of water under this bridge, and a lot of context that if we get it down, should help projects going forward. https://etherpad.openstack.org/p/api-wg-http is a draft outline, and some ideas. I've been slicing chunks off while packing in per bullet patches - https://review.openstack.org/#/q/status:open+project:openstack/api-wg+branch:master+topic:http,n,z But I think that given time on planes, if a few people grabbed a bullet or two before boarding, we could probably get that plane sprinted by the end of the summit. Which would be a great step forward. Commentary welcomed, as always. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
