threa...
>
> cheers, Mike
>
> On 30 Mrz., 09:55, Michele Rossi wrote:
>
> > Hi,
> > is there any way to configure the GWT RPC mechanism to send out fewer HTTP
> > headers with requests?
>
> > In my case the headers account for far more traffic than the RPC
Hey Michele,
maybe this thread will help:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/a95c1eaeb55d2104
cheers, Mike
On 30 Mrz., 09:55, Michele Rossi wrote:
> Hi,
> is there any way to configure the GWT RPC mechanism to send out fewer HTTP
> headers with
Hi,
is there any way to configure the GWT RPC mechanism to send out fewer HTTP
headers with requests?
In my case the headers account for far more traffic than the RPC request
payload.
Many thanks,
Michele
POST http://192.168.151.88:/marketmon/ServiceResolver.gwtrpc HTTP/1.1
Accept
On Monday, December 13, 2010 6:56:31 PM UTC, Thomas Broyer wrote:
>
> See also:
> http://code.google.com/webtoolkit/articles/dynamic_host_page.html
That's a great page. Introduces the method of servlet writing a javascript
variable which is much better than the hidden form variables or cookie
See also:
http://code.google.com/webtoolkit/articles/dynamic_host_page.html
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send emai
Another less optimal option is to let the webserver handle the
redirection based on the HTTP headers, via some sort of extension. Or
instead of writing HTTP headers you could write to the the URL and just
use some sort of Rewrite rule.
--
You received this message because you are subscribed to
s/without hidden/with hidden
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegrou
On Sunday, December 12, 2010 12:37:56 AM UTC, cri wrote:Pete,
I am on the same team as poster. The situation we refer to is the
latter of the two you mention, i.e. based on the users permissions, we
will present one of several GWT views/screens. If we can't do this by
accessing HTTP request header
d to a different page. Is there a reason you prefer to
> code this logic in the client?
>
> If you mean there's just one page after login but depending on the user
> the GWT app will present a different "screen", then that's a different
> problem and something you coul
ent a different "screen", then that's a different
problem and something you could communicate (but HTTP headers wouldn't
be the vehicle of choice).
Thanks,
Pete
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To
decide where the user need to in the app.
Thanks
AP
On Dec 11, 12:03 pm, PeteUK wrote:
> On Saturday, December 11, 2010 5:47:09 PM UTC, skrat wrote:There is
>
> already support for HTTP headers in XHR in GWT, it's the method I
> posted. And it works with all major browsers. Th
On Saturday, December 11, 2010 5:47:09 PM UTC, skrat wrote:There is
already support for HTTP headers in XHR in GWT, it's the method I
posted. And it works with all major browsers. The problem I guess is
that you probably have issues with using RequestBuilder class from your
Spring Roo ap
There is already support for HTTP headers in XHR in GWT, it's the
method I posted. And it works with all major browsers. The problem I
guess is that you probably have issues with using RequestBuilder class
from your Spring Roo app.
--
You received this message because you are subscribed t
andle to the httpheader information in
> my gwt application.
This post intrigued me so I had a look around. As GWT client code will
be Javascript, I searched for how to access the HTTP headers in
Javascript. I found this:
http://stackoverflow.com/questions/220231/accessing-http-headers-in-javascrip
I assume you mean Spring Roo + GWT? In that case I can't help you,
heard of it before but never used it, quickly checked it out, seems
like lots of scaffolding is going on there, so you will have to
customize. RequestBuilder class can make requests of any method btw (as
long as browser supports tha
Thanks for the response. May be I am missing something but this class
seems to be for making a Get request. To add some more information, I
have a spring + gwt application.
On Dec 10, 3:18 pm, skrat wrote:
> http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/g...,
> java.lang.Str
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/http/client/RequestBuilder.html#setHeader(java.lang.String,
java.lang.String)
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to goog
I have just started on the GWT 2.1 application. We have a single sign
on done by a tool that passes the credentials in the HTTPHeader. Based
on the credentials, different users need to be directed to different
landing pages. How can I get a handle to the httpheader information in
my gwt application
On Feb 17, 6:58 pm, chillyspoon wrote:
> Hi everyone,
>
> Does anyone know how to add HTTP headers to the HTTP POST that gets
> kicked off when a FormPanel submit method is called?
No, that's not possible. FormPanel is just an HTML , so it obeys
the same rules and constrain
Hi everyone,
Does anyone know how to add HTTP headers to the HTTP POST that gets
kicked off when a FormPanel submit method is called?
I need to add custom headers that modify server behavior..
Thanks,
Chilly.
--
You received this message because you are subscribed to the Google Groups
20 matches
Mail list logo