[
https://issues.apache.org/jira/browse/HUPA-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761325#action_12761325
]
Manuel Carrasco commented on HUPA-30:
-------------------------------------
It would be nice the ability to configure timeouts in hupa rpcs, but
gwt-presenter doesn't support it.
So in the case of network connectivity errors (wifi unavailable, firewall ...)
it takes a long to realise the server is down.
> [patch] Detect server status and reuse server session
> -----------------------------------------------------
>
> Key: HUPA-30
> URL: https://issues.apache.org/jira/browse/HUPA-30
> Project: JAMES Hupa
> Issue Type: Improvement
> Components: client, server
> Reporter: Manuel Carrasco
> Assignee: Norman Maurer
> Attachments: patch_check_server_status.diff
>
>
> This patch:
> - Checks the status of the server each time that an error occurs in a rpc
> action. So far It is implemented in LogoutUser and Noop actions.
> - Updates a notification message in the top of the screen with the status of
> the server when it gets unreachable, and removes it when it becomes
> accessible.
> - Reuses remote session in the case of the application is reloaded.
> - Demonstrates that sessionId cookie or Session class are not needed since
> JSESSIONID is enough.
> - Fixes issue #Hupa-4
> Once this patch is applied, I'll refactor the session logic in order to
> remove Session class and simplify session tracking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
