Hi,
On Tue, Aug 27, 2019 at 9:20 PM Ram C <
time...@gmail.com> wrote:
>
> Hi Simone,
>
> I noticed cometd connection broken message in the browser console log while in debug mode. (breakpoint set in chrome). Since the /meta/connect message is not received in given time the server marked the connection broken and cleanup the session.
That is a *long* network failure, not a short one.
> When the client re-established the long poll, is there a way to send the undelivered messages from server?
CometD by default does not store in a persistent way the messages
destined to a client, because the client may never show up again and
the messages will be stored indefinitely, etc.
However, if you need such feature, which is highly application logic
dependent (and that is the reason why CometD does not implement it -
whatever solution won't work for all cases), you can implement it
yourself by using CometD listeners: for example, whenever a message is
added to the queue for a remote client, you store it into a persistent
storage.
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.