If I've loaded of Botkit Starter Web locally or in the cloud and refresh the browser, the client.js sends down a hello or a welcome_back event.
In the ingest middleware in Web.js when finding the conversation there is a section that changes the event to reconnect instead of keeping it as welcome_back.
As an end user, I think it would make more sense for welcome_back to pass through if the reconnect is happening due to a page refresh by the client.
If the network is intermittent and disconnects and then reconnects then in that case a reconnect event makes sense.
Is there a clean way to distinguish between these two types of disconnects?
A voluntary client page refresh vs. network connectivity issues?
If I've loaded of Botkit Starter Web locally or in the cloud and refresh the browser, the
client.jssends down ahelloor awelcome_backevent.In the
ingestmiddleware inWeb.jswhen finding the conversation there is a section that changes the event toreconnectinstead of keeping it aswelcome_back.As an end user, I think it would make more sense for
welcome_backto pass through if the reconnect is happening due to a page refresh by the client.If the network is intermittent and disconnects and then reconnects then in that case a
reconnectevent makes sense.Is there a clean way to distinguish between these two types of disconnects?
A voluntary client page refresh vs. network connectivity issues?