|
This is not the normal behaviour of any web site.
When a session timeouts in a standard web site, the site responds informing that the session has expired AND redirects the user to the login page. The application DOES NOT REDIRECT to the login page, leaving the user stuck in a non working application. This is absolutelly wrong and usesless. Ok. I didn't understand you the first time.
BasicResult returned by server does not contain the proper resultCode (SESSION_INVALID or SESSION_TIMEOUT), so client can not find out when to redirect user to login screen
Now, all the session exceptions are throwed from the BasicCommand method 'execute' before to call the explicity method and catched in the associated service.
The services, depending on the exception, fill the BasicResult.ResultCode argument to be treated by the Flex Client. (Return to the Login screen in the Timeout case). |
||||||||||||||||||||||||||||||||||||||
All the functionalities less login, requires that the session is active.
If this session is not active the user must log in.
Do you consider that it's not correct? If not, please, propose an alternative
Thanks