Regarding REST response formats

[haris al <ha...@gmail.com>]

Hi,

I tried getting REST responses from the shindig server ( java ) version .
There are different formats available. I  got json and xml responses
successfully
for /people/guid/@all . But the two responses are having different number of
elements. For xml the element tree is more than json. In xml the data
contain empty elements .Not in json.Is it because the json response will
contain only data rich elements ? or Is that response content is different
for xml and json ?

If i am using any client application which communicate with the shindig
server , which response is better json or xml ?

Regards
Haris

Re: Regarding REST response formats

[Ian Boston <ie...@tfd.co.uk>]

There is a blocker out on this issue to make the output conform to  
the XSD for 0.8.1 (nearly done.)
unfortunately, the XSD produces XML that does not match the json and  
so there is discussion about clearing this up and converging on the  
portable contacts spec on the opensocial spec list. This convergence  
may happen in 0.9 of the spec, but for the moment, Shindig is  
implementing 0.8.1

If you want to try the newer (unfinished) bean converter switch  
BeanXmlConverter to BeanXstreamConverter in the Guice modules.

Ian

On 23 Oct 2008, at 12:35, haris al wrote:

> Hi,
>
> I tried getting REST responses from the shindig server ( java )  
> version .
> There are different formats available. I  got json and xml responses
> successfully
> for /people/guid/@all . But the two responses are having different  
> number of
> elements. For xml the element tree is more than json. In xml the data
> contain empty elements .Not in json.Is it because the json response  
> will
> contain only data rich elements ? or Is that response content is  
> different
> for xml and json ?
>
> If i am using any client application which communicate with the  
> shindig
> server , which response is better json or xml ?
>
> Regards
> Haris