Then you have to put the session ID into the URL when the browser is
making a request on behalf of you - for example, you want your user to
display a private (password protected) image, or download a private
document.
Other than that, your f) is my c) without using the cookies as
persistent
Option f) don't use session cookies (or servlet sessions).
1) Login to the server via RPC call.
2) Successful login RPC returns a session ID, put the session ID in a
Java static or JS global variable.
3) Pass the session ID in all RPC calls where it matters.
4) Profit.
Your server should be as
a) start your FF with -P and create different profiles, then start it
with -P --no-remote and pick a profile - profiles don't share session
cookies. (PITA, only FF)
b) use virtualization and run one FF and one IE8 in each instance
(requires RAM)
c) bake your own session cookies - when your app
Hi,
I have a problem with GWT and Firefox 3 and IE 8 browsers.
I have an application developed in GWT.
1. I open Firefox / IE browser and login with valid credentials and
it works fine.
2. I keep this session open and open other new Firefox / IE Browser
window and i login with different
