However, keep in mind that GET requests are quite limited. For example, IE
cannot handle a URL longer than 2083 characters. Thus, not very much
information can be serialized into a URL. Hence, most forms are usually
POST'd, not GET'd.
Joe
--
You received this message because you are subscrib
On Mon, Apr 23, 2012 at 11:20 PM, LogicalGoetz wrote:
> This may be a terribly novice question, but for each POST performed
> by, say, a FormPanel, is there a subsequent HttpResponse generated by
> the Servlet?
>
> Obviously in standard situations this will play out as follows:
> -client makes a P
I've run into this exact problem before, but not while using GWT. I found
that for XHR's, Post 1 must return before Post 2 can return. I'm not sure
why this it, but it seems to be the case at least on FF and Chrome.
My use case was to:
- Post 1 - start a long running task
- Post 2 - Check
Interesting question... see comments below
On 4/23/2012 2:20 PM, LogicalGoetz wrote:
This may be a terribly novice question, but for each POST performed
by, say, a FormPanel, is there a subsequent HttpResponse generated by
the Servlet?
Obviously in standard situations this will play out as foll
This may be a terribly novice question, but for each POST performed
by, say, a FormPanel, is there a subsequent HttpResponse generated by
the Servlet?
Obviously in standard situations this will play out as follows:
-client makes a POST request
-servlet handles the request
-servlet sends POST respo