handling a lost comms of server on the client side

Added by Billy Muma over 1 year ago

I've been learning to use wt for a while now and i am very pleased with the framework.

The LoadingIndicator is a good way of providing feedback to the user typically when
we are waiting for the server to respond.

I think it would be useful to have a use case similar to the LoadingIndicator
where a client-side wt application identifies that it can no longer communicate
with its server, and produce a 'ServerLostIndicator' that would attempt to
reconnect every x seconds.

if the server was restarted, all session information is lost anyway and
reconnecting would yield a completely new session.

if comms were down temporarily for whatever reason, reconnecting would restore the
session.

Any thoughts?

Can be this be implemented with the current state of Wt? ( maybe my skill level with
wt, js and c++ prevent me from seeing something very obvious )


Replies

RE: handling a lost comms of server on the client side - Added by Koen Deforche over 1 year ago

Hey Billy,

You are not overlooking anything.

While the client will already retry failed connections (using an exponential back-off algorithm), the loading indicator should have support for providing an appropriate message.

Can you make a feature request for this ?

Regards,
koen