| User-Sessions Explanation [message #110790] |
Wed, 29 October 2008 18:16  |
 Austin Riddle
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Hello,
I just wanted to start by telling the RAP team how appreciative our SD
team is of all of the work that has been done on this very exciting
Eclipse project. As we pour through the code, we are continually reminded
of how much of an initial investment was made.
Now to business,
In testing our RAP application, my team-members and I have experienced
issues that seem to point to our lack of understanding about the lifecycle
of user-sessions. Can anyone explain some details about the user-session
lifecycle?
In our experience, when a user loads accesses application, a new workbench
(session-singleton) is created each time.
When the user closes their browser, the session stays active until the
session timeout is reached (which we have set to 5 minutes).
When the session terminates, the workbench is then shutdown.
In particular, we want to know the following:
1. Why do we sometimes when accessing our application receive the white
page saying our session has expired and the user should click "here" to
restart it?
And under what circumstances should we expect such a message?
2. Under what conditions (if any) would a user be able to re-connect to a
session/workbench on the server?
3. In terms of sessions, what exactly happens when the user closes their
browser?
4. This is related to number 3, but under what conditions does a client
receive the "The server seems to be temporarily available, would you like
to retry? OK/Cancel"? When you click OK, what should happen? When you
click cancel what should happen? Sometimes if we experiment in IE7 by
unplugging the network cable and then click OK on the dialog after
restoring the connection, we get the "Multiple browser instances are not
allowed." In Firefox 3 we get no retry dialog, but rather a page that
says "Request failed: status code 0" for the same test case. In looking at
Request.js in the q07 plugin, we find that it is expecting a -1 to prompt
with a retry.
Our particular session-related problems occur when testing over a poor
wireless connection or testing a momentary lost connection.
Any help on these questions is very appreciated.
Thanks for your time.
|
|
|
|
| Re: User-Sessions Explanation [message #110840 is a reply to message #110790] |
Thu, 30 October 2008 08:23  |
Eclipse User |
|
|
|
Originally posted by: rherrmann.innoopract.com
Austin Riddle wrote:
> Hello,
>
> I just wanted to start by telling the RAP team how appreciative our SD
> team is of all of the work that has been done on this very exciting
> Eclipse project. As we pour through the code, we are continually
> reminded of how much of an initial investment was made.
> Now to business,
>
> In testing our RAP application, my team-members and I have experienced
> issues that seem to point to our lack of understanding about the
> lifecycle of user-sessions. Can anyone explain some details about the
> user-session lifecycle?
>
> In our experience, when a user loads accesses application, a new
> workbench (session-singleton) is created each time.
> When the user closes their browser, the session stays active until the
> session timeout is reached (which we have set to 5 minutes).
> When the session terminates, the workbench is then shutdown.
>
> In particular, we want to know the following:
>
> 1. Why do we sometimes when accessing our application receive the white
> page saying our session has expired and the user should click "here" to
> restart it?
> And under what circumstances should we expect such a message?
If you get his message while the server-session is still alive, it
is probably a bug. Feel free to file a bugzilla if you can reproduce it.
Otherwise, start a session, wait six Minutes doing nothing, try to
interact with the application => you will see the message since the
server session was cleared one Minute ago.
>
> 2. Under what conditions (if any) would a user be able to re-connect to
> a session/workbench on the server?
RAP does currently not provide a way to re-connect to a session.
As of now, once the user has closed the browser window, there is no
way to re-gain access to the server-session.
>
> 3. In terms of sessions, what exactly happens when the user closes their
> browser?
Nothing immediately, five Minutes later (in your case) the server
session will be cleared.
> 4. This is related to number 3, but under what conditions does a client
> receive the "The server seems to be temporarily available, would you
> like to retry? OK/Cancel"? When you click OK, what should happen? When
> you click cancel what should happen? Sometimes if we experiment in IE7
> by unplugging the network cable and then click OK on the dialog after
> restoring the connection, we get the "Multiple browser instances are not
> allowed." In Firefox 3 we get no retry dialog, but rather a page that
> says "Request failed: status code 0" for the same test case. In looking
> at Request.js in the q07 plugin, we find that it is expecting a -1 to
> prompt with a retry.
> Our particular session-related problems occur when testing over a poor
> wireless connection or testing a momentary lost connection.
> Any help on these questions is very appreciated.
>
> Thanks for your time.
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03440 seconds
] 
Search
Help
Register
Login
Home
