GWT has a bug that prevents it from being use with Restlet. The
Restlet framework has direct support for both Appengine, as a service
provider, and GWT as a client. However, a bug added to GWT since 1.7
makes it impossible to use GWT with a restlet server if you want to
use XML representations.
On 9 juil, 17:18, ivar vasara wrote:
> On Jul 9, 7:02 am, Stefan Bachert wrote:
>
> > I guess directly supporting RESTful/Soap does not make much sense
> > because of SOP and other security topics.
>
> With browsers becoming more aware and supporting sources from multiple
> sources, SOP is not
> With browsers becoming more aware and supporting sources from multiple
> sources, SOP is not so much an issue.
first of all SOP is a browser topic not an GWT.
I don't think that browsers will give up security.
> That is a sad state of affairs and ties the client to a GWT-RPC
> speaking backend.
On Jul 9, 7:02 am, Stefan Bachert wrote:
> I guess directly supporting RESTful/Soap does not make much sense
> because of SOP and other security topics.
With browsers becoming more aware and supporting sources from multiple
sources, SOP is not so much an issue.
> At this time I would recommen
Hi Marius,
I guess directly supporting RESTful/Soap does not make much sense
because of SOP and other security topics.
At this time I would recommend always to use GWT-RPC to communicate.
>From the server SOP does not apply and you can access any webservice
you like.
Stefan Bachert
http://gwtwor
Hi,
A lot of web APIs use REST nowadays. GWT seems really well suited to
build mashups/UIs on top of REST web services.
However, it's not that easy to work with REST from GWT (see also
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/71f2d5599ee2593f/41ef729a5d1cfe8d?lnk=gst
