<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 21, 2013 at 3:46 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="im"><div>On Jun 21, 2013, at 12:38 PM, Doug Hellmann <<a href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 20, 2013 at 2:00 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div>On Jun 20, 2013, at 10:22 AM, Brant Knudson <<a href="mailto:blk@acm.org" target="_blank">blk@acm.org</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div><div><div>How about a mapping of JSON concepts to XML like:<br><br>collections:<br></div><object> <pair name="pair-name"> the-value </pair> ... </object><br>
</div><array> <element> the-value </element> ... </array><br><br></div><div>values:<br></div><string>text</string><br></div><true/><br></div><false/><br></div><null/><br>
</div><number>number</number><br><br></div>This type of mapping would remove any ambiguities. Ambiguities and complexity are problems I've seen with the XML-JSON mapping in Keystone. Plus the fact that it's so not-XML would convince users to switch to JSON. With a simple mapping, I don't think it would be necessary to test all the interfaces for both XML and JSON, just test the mapping code.<br>
</div></blockquote><div><br></div></div>+1 for something like this. JSON primary + autgenerated XML. I think the ideal version would be autogeneration of xml from jsonschema and some method for prettifying the xml representation via jsonschema tags. The jsonschema + tags approach is probably a bit further off (maybe for v4?), so having an auto conversion which is ugly but functional seems better than no XML support at all.</div>
<div><br></div><div>Vish</div></div></blockquote><div><br></div><div>Let's please not invent something new for this. We're building a high level platform. We shouldn't have to screw around with making so many low level frameworks to do things for which tools already exist. WSME will handle serialization, cleanly, in both XML and JSON already. Let's just use that.</div>
<div><br>Doug</div></div></div></div></blockquote><div><br></div></div>Doug,</div><div><br></div><div>Switching to WSME for v3 is out of scope at this point I think. Definitely worth considering for v4 though.</div><div>
<br></div><div>Vish</div></div></blockquote><div><br></div><div style>Absolutely - we agreed about that weeks ago. I assumed, however, that decision meant we would just continue to use the existing serialization code. I thought this discussion was moving toward writing something new, and I wanted to head that off.</div>
<div style><br></div><div style>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="h5"><div><br><blockquote type="cite">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div>
<br><blockquote type="cite">
<div dir="ltr">
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 20, 2013 at 11:11 AM, Jorge Williams <span dir="ltr"><<a href="mailto:jorge.williams@rackspace.com" target="_blank">jorge.williams@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
On Jun 20, 2013, at 10:51 AM, Russell Bryant wrote:<br>
<br>
> On 06/20/2013 11:20 AM, Brian Elliott wrote:<br>
>> On Jun 19, 2013, at 7:34 PM, Christopher Yeoh <<a href="mailto:cbkyeoh@gmail.com" target="_blank">cbkyeoh@gmail.com</a>> wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>> Just wondering what people thought about how necessary it is to keep XML support for the Nova v3 API, given that if we want to drop it doing so during the v2->v3 transition is pretty much the ideal time to do so.<br>
>>><br>
>>> The current plan is to keep it and is what we have been doing so far when porting extensions, but there are pretty obvious long term development and test savings if we only have one API format to support.<br>
>>><br>
>>> Regards,<br>
>>><br>
>>> Chris<br>
>>><br>
>><br>
>> Can we support CORBA?<br>
>><br>
>> No really, it'd be great to drop support for it while we can.<br>
><br>
> I agree personally ... but this has come up before, and when polling the<br>
> larger audience (and not just the dev list), there is still a large<br>
> amount of demand for XML support (or at least that was my<br>
> interpretation). So, I think it should stay.<br>
><br>
> I'm all for anything that makes supporting both easier. It doesn't have<br>
> to be the ideal XML representation. If we wanted to adopt different<br>
> formatting to make supporting it easier (automatic conversion from json<br>
> in the code I guess), I'd be fine with that.<br>
><br>
<br>
<br>
</div>I agree, we can change the XML representation to make it easy to convert between XML and JSON. If I could go back in time, that would definitely be something I would do different. 3.0 gives us an opportunity to start over in that regard. Extensions may still be "tricky" because you still want to use namespaces, but having a simpler mapping may simplify the process of supporting both.<br>
<br>
-jOrGe W.<br>
<div><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></blockquote></div><br></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>