Avatar

Server Connection messages on the Header of the site

0

Can you please explain in detail the meaning of the server connection messages that pop up on the header.  ("Whew, we are back online", "Trying to reach the server", "Connection is unreliable").  Are these messages in reference to your "comet" channels and if you lose a packet the client is getting a response like this.  It is very confusing and disturbing to the customer.  It seems to point to problems where there are none at times and paints a bad picture.

This is coming from several large customers.

Thanks,

Michael

Michael Head

Please sign in to leave a comment.

5 comments

0
Avatar

Michael,

"Connection is unreliable" message is shown when any of our web requests (get data, get page, comet/websocket notifications connection) fails for the first time. By first time, we mean that there was a successful request just before the first failure. When it fails for the first time, you will see the warning come through in yellow color but will disappear as soon as the next request succeeds. If the next request does not succeed, we switch to the following error-style messages:

"Trying to reach the server..."

"No success so far, but we're still trying to connect..."

"Still trying to reach the server..."

We show them one by one when 2 or more requests are failed in a row. As soon as there's successful request, we will then display "Whew! We're back online".

Dom 0 votes
0
Avatar
Thanks. To my point though. This can be too much information for the user at times and lead to confusion. Sometimes it could be just transient errors and the user sees this and thinks the Server is going down all the time.
Michael Head 0 votes
0
Avatar

Yes, I see your point as well and I will open a feature request in regards to this. 

Dom 0 votes
0
Avatar

Michael,

Have you noticed if these messages occur more often in one type of browser than others from your clients? We want to check if a particular browser would cause more false alarms than others.

Dom 0 votes
0
Avatar

I am not sure.  I know they use IE 10 and FireFox and Chrome.  Maybe run some tests on large clients with each browser on your dev machines.  Also try outside of your intranet.

Michael Head 0 votes