Jay, I’ll +1 to that. As I’ve been tinkering with potential Pecan support for the Nova API, I’ve run into the same issue w/ the API composition being seriously complicated (to the point where I’ve realized Pecan isn’t the hard part, it’s the bunch of cruft you need to tie in Pecan/Routes/Falcon/<fill in WSGI framework here>).
--- Ryan Petrello Senior Developer, DreamHost ryan.petre...@dreamhost.com On Jan 13, 2014, at 9:23 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On Sun, 2014-01-12 at 19:52 -0800, Christopher Yeoh wrote: >> On my phone so will be very brief but perhaps the extensions extension >> could publish the jsonschema(s) for the extension. I think the only >> complicating factor would be where extensions extend extensions but I >> think it's all doable. > > Am I the only one that sees the above statement as another indication of > why API extensions should eventually find their way into the dustbin of > OpenStack history? > > -jay > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
