Thanks for the quick answer, Joscha Krutzki<br><br><div><span class="gmail_quote">2007/3/23, Balazs Ree <<a href="mailto:ree@ree.hu">ree@ree.hu</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 23 Mar 2007 13:12:45 +0100 Joscha Krutzki wrote:<br><br>> I would like to reuse the jsonserver Zope3 product to generate a Exhibit<br>> Json view of objects<br>> and to make a plone view with Exhibit filtering for objects.
<br>><br>> But you are the one who are making the plone javascript framwork, so I<br>> need your opinion.<br>> Are you planing to support json?<br><br>I don't have time now at all but I will react to your letter next week.
<br><br>I am also one author of the jsonserver product, I also followed and<br>participated in the discussion of the new jsonrpc working draft's<br>proposal on Zope's side. Json and jsonrpc are supported by kss from the
<br>very beginning. This means that if the jsonserver product is detected the<br>transport changes from default xml to the jsonrpc protocol. This is<br>different though from what you aim at.<br><br>We had different reasons not to spend much time on this issue:
<br><br>1. We wanted to be as much independent from server side components as<br>possible in the framework, and at the moment XML seemeed a more<br>widespread web standard than json. (This is actually not entirely true<br>
any more in my opinion.)<br><br>2. It is really totally transparent on the kss application level, what<br>transport is used physically: json or xml. So noone really notices the<br>difference. We could have the possibility to marshall more complex data
<br>types with json in the transport (kss commands), but then we would be<br>locked to use json from that moment, and loose xml. If we wanted to add<br>the handling of complex variables to xml otoh, we would end up<br>reimplementing json which is pretty pointless so here is one point where
<br>json may come back.<br><br>I believe recently we removed the json support from kss because it did<br>not seem to have any interest to maintain it and it costed too much work.<br><br>On the other hand using json on different other levels in kss may make
<br>lots of sense.<br><br>> Is it a good thing to integrate a json view of content objects in KSS?<br>> Is it possible to support the Exhibit library in KSS?<br><br>I cannot react to this because I would need much more time to answer.
<br>Mainly I have to look at Exhibit. So please in case I forget to react,<br>let me remember, and let's get back to this soon.<br><br>--<br>Balazs Ree<br><br>_______________________________________________<br>Kss-devel mailing list
<br><a href="mailto:Kss-devel@codespeak.net">Kss-devel@codespeak.net</a><br><a href="http://codespeak.net/mailman/listinfo/kss-devel">http://codespeak.net/mailman/listinfo/kss-devel</a><br></blockquote></div><br><br clear="all">
<br>-- <br>Joscha Krutzki<br>Adalbertstr. 73 <br>10997 Berlin<br>030/63226730<br>0179/7466360<br>[ Link zur Vcard: <a href="http://jokasis.de/Joscha_Krutzki.vcf">http://jokasis.de/Joscha_Krutzki.vcf</a> ]