On Jun 3, 2011, at 1:13 PM, Bryan Taylor wrote:
> We've standardized on XML for backend work. We aren't spending much time
> debugging serialization issues and are pretty happy with our decision and
> aren't likly to change any time soon
vs.
> So the obvious thing to do is support both JSON and XML, which isn't that
> hard.
I'm always confused when people claim that doing something is easy, but
also that for them to do the same thing is too hard.
> at the point they try to tell me how to implement my solutions, all it does
> is annoy me, because format wars are annoying.
I'm not sure if you intended it, but dismissing a discussion about
taking on a significant chunk of work as nothing more than an annoying "format
war" sounds rather condescending. We're not arguing the merits of of one over
the other; we're deciding if we are going to commit to supporting XML right
now, or perhaps add it later on.
Everyone would love to support as many formats as possible. With
limited resources, we need to narrow our focus. And since this is all open
source, anyone who has a need and finds implementing the solution for that need
isn't "that hard" is more than welcome to contribute.
-- Ed Leafe
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
