The connection will stay open if someone's browser is open with the dashboard, - The nature of SignalR is that its' a web socket connection, So it will remain open while your browser is active on the backoffice (i think).
Its a little odd because for me during testing its usually the other way around and it closes after a while being idle, when i want to check something
in terms of uSync the signalR connection is only used for informational purposes (to show progress when you import/export). if the connection actually fails the whole thing still works, and no 'commands' can be sent via the SignalR hub that uSync uses that will send anything out.
uSync Complete - very long signalr connections
Hi Kevin
Our infra team have quizzed me about signalr calls as below that in some cases has lasted up to 6 hours.
Any idea why these connections would stay open for so long?
Regards
Jules
Hi Jules,
The connection will stay open if someone's browser is open with the dashboard, - The nature of SignalR is that its' a web socket connection, So it will remain open while your browser is active on the backoffice (i think).
Its a little odd because for me during testing its usually the other way around and it closes after a while being idle, when i want to check something
in terms of uSync the signalR connection is only used for informational purposes (to show progress when you import/export). if the connection actually fails the whole thing still works, and no 'commands' can be sent via the SignalR hub that uSync uses that will send anything out.
is working on a reply...