On Aug 28, 2010, at 11:03 AM, Jorge Williams wrote: > I see standardization as being extremely beneficial. Having a common > language framework is one example of how standardization can help us, but > it's important to also think of this from the perspective of our clients -- > why should they have to learn 10 different ways of doing the same thing? >
Having standard higher level bindings is fine as long as there are also domain-specific lower level bindings. Think of it like ORM vs. direct SQL. Many (most?) applications are fine with an ORM, but it gets really frustrating for other applications if that's all that's available. But aside from all that, I don't think bindings really belong lumped into an OpenStack Commons project but instead as a bindings project per service (such as Swift Bindings as a project, comprised of packages for each of the languages supported). The main reason for a project separate from the service is that bindings almost always have a quicker release schedule. In my opinion, keeping standard behaviors in the higher level bindings should be done with an outside specification, I suppose such could live in OpenStack Commons just fine, but likely wouldn't have any code, or very little, directly associated with it. -- gholt has now spent 2 cents -- _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
