Hi Clemens,
if I understand you correctly, in such a case you prefer to resend the
last failing request instead of complete restart of the application. Is
this correct? Such functionality exists in case of "connection error"
[1]. It seems that in your case the error is "request failed". You can
patch (at runtime) the ErrorHandler.js#_getErrorBoxData to make "request
failed" case to behave like "connection error".
[1]
https://github.com/eclipse/rap/blob/master/bundles/org.eclipse.rap.rwt/js/rwt/runtime/ErrorHandler.js#L343
Best regards,
Ivan
On 3/28/2019 10:45, Clemens Eisserer wrote:
Hi,
RAP depends on client and server being in sync which in theory
shouldn't be a problem.
However in real-world we are facing situations where users e.g.
disconnect their notebook from the docking station (and the notebook
immediatly re-connects to wlan) or where the LTE network re-connects
to another base-station and for a few seconds the connection is
disrupted.
Currently, in case there was a request in progress, the RAP
application displays the server-not-available popup, and "restart"
completly restarts the application.
I wonder - is that really nescessary? The state on the server is still
there, wouldn't it be possible to simply restore the state on the
client based on what is still on the server?
Best regards, Clemens
_______________________________________________
rap-dev mailing list
rap-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/rap-dev
_______________________________________________
rap-dev mailing list
rap-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/rap-dev
