I've been experimenting with server push and noticed that if I kill the server, I get no feedback in the browser to indicate that there is a problem with the connection.
I can see that when I restart the server the sequence of successful (i.e. 200 OK) requests to /zkau/comet?dtid=... resumes, but the previous session died when the server was killed and I get no feedback in the UI to let the user know that the old desktop is no longer available.
In our application it is important that if the push connection is broken, the user should be given some notification of the problem.
I am considering to integrate it with https://sourceforge.net/tracker/?func=detail&aid=2874459&group_id=152762&atid=785194
But it was targeting at 5.0. What version of ZK are you expecting this feature to be?
Ready since 10/13
---
There are two types of errors: session timeout (including server restart) and disconnect (such as timer shutdown, network broken).
For the first type, you can specify the URI to redirect to
<client-config>
<error-reload>
<device>ajax</device>
<error-code>410</error-code>
<reload-uri>/timeout.zul</reload-uri>
<connection-type>server-push</connection-type>
</error-reload>
</client-config>
For the second type, it will invoke confirmRetry (JavaScript -- just like AU did). You can override confirmRetry to show the message you want.
With ZK 5, we are going to allow a fragment of HTML to be popup at the client (https://sourceforge.net/tracker/?func=detail&aid=2874459&group_id=152762&atid=785194)