Hi Sri, I mean of course, that there would have to be a component (e.g. Servlet) on the server side, that re-translates the get request, and then calls the RemoteServlet (or something underlying), as if a usual GWT-RPC request had been issued. Se we would basically use JSONP as a tunnel.
[The defense against CSRF would have to be done using a separate technique, but let's forget about that for a moment.] Chris On Jun 16, 9:42 pm, Sripathi Krishnan <[email protected]> wrote: > No, it won't. > > 1. GWT RPC exclusively uses POST. JSONP uses a <script> tag, which is > essentially a GET request. You can't make a POST request using a script > tag. > 2. RPC adds custom http headers to the request (X-GWT-Permutation, or > something like that). You cannot setup custom http headers using a script > tag, or anyother html tag. > > Because of these two, RPC cannot be wrapped in a JSONP call. > > The restrictions on the URL length are not that prohibitive. GWT supported > browsers allow atleast 2KB, with the newer ones allowing more. That usually > is sufficient for most RPC calls. > > --Sri -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
