And how can i track the session id? I can store the sessionId at the
client-side (for users which have cookies disabled), but if they
reload the client-side the sessionId will be lost.
So, what do you think: Will it be a good solution to add the
sessionId into the URL to enable session tracking
Any ideas? Or would you recommend to use Cookies only?
On 22 Mrz., 16:12, Johannes Stein johannes.st...@googlemail.com
wrote:
And how can i track the session id? I can store the sessionId at the
client-side (for users which have cookies disabled), but if they
reload the client-side the
Read this
http://code.google.com/p/google-web-toolkit-incubator/wiki/LoginSecurityFAQ
http://code.google.com/p/google-web-toolkit-incubator/wiki/LoginSecurityFAQ
2011/3/22 Johannes Stein johannes.st...@googlemail.com
And how can i track the session id? I can store the sessionId at the
But if i have two seperate modules each client will get a different
sessionId from the server (rpc-call), because the servers interprets
each module as a single client!?
On 16 Mrz., 20:00, Johannes Stein johannes.st...@googlemail.com
wrote:
No ideas?
On 16 Mrz., 18:58, Johannes Stein
It depends how session management is done on the client. If you use cookies
to store the session id it should make no difference as long as you
communicate with the same domain (Cookies are domain specific).
If you open gmail in two tabs in your browser you won't have to authenticate
twice
Cookies are fine, but what happens if cookies are disabled?
Then two sessions will be created by the server, or not?
On 17 Mrz., 12:40, Uemit uemit.se...@gmail.com wrote:
It depends how session management is done on the client. If you use cookies
to store the session id it should make no
No. SessionId is create.
2011/3/17 Johannes Stein johannes.st...@googlemail.com
Cookies are fine, but what happens if cookies are disabled?
Then two sessions will be created by the server, or not?
On 17 Mrz., 12:40, Uemit uemit.se...@gmail.com wrote:
It depends how session management is
The modules is in client side. Session is in the server side.
Juan
2011/3/16 Johannes Stein johannes.st...@googlemail.com
hello,
im implementing a little online-game with gwt.
this game contains two modules - one ui for the game itself and a
seperate user-area.
if a user is logged-in into
Yes, thats right.
But will it then be possible to make in each module a gwt-rpc-call
which checks, if the user is logged-in?
Will the Session be the same, or will each call (from different
modules) deliver a different session-id?
And what happens, if the users browser has cookies disabled? Is
No ideas?
On 16 Mrz., 18:58, Johannes Stein johannes.st...@googlemail.com
wrote:
Yes, thats right.
But will it then be possible to make in each module a gwt-rpc-call
which checks, if the user is logged-in?
Will the Session be the same, or will each call (from different
modules) deliver a
But will it then be possible to make in each module a gwt-rpc-call
which checks, if the user is logged-in?
Yes, is possible.
Will the Session be the same, or will each call (from different
modules) deliver a different session-id?
I handle this with Spring security, is transparent. If you don't
11 matches
Mail list logo
