hi Thierry, I've examined the sample GWT app you mentioned below, but It is not demonstrating the problematic case of POST -
First, the sample is only fetching a json object from the server side via the GET operation Second - there is no update back to the server (which is what is not working as expected in my case - specifically via Ajax POST ) Is there any actual difference between posting via Ajax rather than via web forms submitting? doesn't it all get translated down to a HTTP POST request and the body is url-encoded in both cases with the content type being application/x-www-form- urlencoded? It is not clear to me why I need a custom converter? I reviewed your sample code and there is nothing specific there, looks like infrastructure stuff... isn't it always needed in case of HTTP POST operations? First, unbox the encoded body and then send it to be translated into the Object via the toObject method? again - I believe this is relevant for Ajax as well as Web Forms in case we use the POST rather then the GET. btw - GET operations are very limited since you cannot upload large JSON objects because of URL length limitations (especially on mobile devices) Thanks, Chen. On Tue, Apr 13, 2010 at 12:38, Chen Bekor <[email protected]> wrote: > hi, > > I'm just trying it out to see where are the differences. > > I will let you know once I have conclusions, > > Best, > > Chen. > > > On Tue, Apr 13, 2010 at 12:29, Thierry Boileau < > [email protected]> wrote: > >> Hi Chen, >> >> did you have a look at this sample application? >> http://wiki.restlet.org/docs_2.0/13-restlet/188-restlet.html >> It illustrates basic JSON parsing. >> >> Best regards, >> Thierry Boileau >> >> ------------------------------------------------------ >> >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2580612 >> > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2580744
