On Mon, 2014-01-13 at 09:40 -0500, Ryan Petrello wrote: > 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>).
Indeed. And don't get me wrong... I'm not at all saying that Chris is to blame for anything (or any one person in particular). Just pointing out that, IMO, the usefulness of API extensions is outweighed by the added complexity and churn that they bring with them. -jay > --- > Ryan Petrello > Senior Developer, DreamHost > [email protected] > > On Jan 13, 2014, at 9:23 AM, Jay Pipes <[email protected]> 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 > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
