On 06/08/2013 14:46, Jay Pipes wrote:
API extensions are more hassle than anything else. Let us promote standards, not endless extensibility at the expense of usability.
This is the crux of the issue. Everyone who participates in standardisation meetings has their own agenda to follow: their preferences, likes, dislikes, must have features, etc. This is why standards end up with optional extensions. If you dont have them, then you cannot get buy in from sufficient stakeholders. If you do have them, then you end up with extensibility.
But actually extensibility in my opinion is a "must have" feature, since no protocol or standard (or Keystone) remains static for ever, and new features are continually being added to it. Therefore you must have a way for clients to know what functionality the remote server currently supports so that it can talk the correct protocol flavour to it.
regards David
Best, -jay
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
