You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a scenario where I need to say if the server can not be found, then use a different mode. So I publish a message when the page loads and handle the transport:up and transport:down events. I set a flag to say if transport is up or down based on which event gets raised. If transport:down is raised I start a timer and when the timer executes if the transport is not up, I need to stop trying to reach the server. I am calling:
The transport:{up,down} events are informational and should not be used to drive business logic, especially not for delivery correctness. You should take a look at the scheduler docs which explain how to override how deliveries and retries work.
Hi there,
I have a scenario where I need to say if the server can not be found, then use a different mode. So I publish a message when the page loads and handle the transport:up and transport:down events. I set a flag to say if transport is up or down based on which event gets raised. If transport:down is raised I start a timer and when the timer executes if the transport is not up, I need to stop trying to reach the server. I am calling:
client.disconnect();
client.disable();
client = null;
But that first message that was published keeps retrying over and over for ages.
How can I get Faye to stop trying that message?
Thanks for your time.
The text was updated successfully, but these errors were encountered: