Concurrent sessions from the same browser

[yaodaniel]

Hello,

I'm using lex-web-ui and have a working website with it running in an iframe. While testing I noticed that if I were to open my website in multiple tabs in the same browser and try to send messages all at once in each tab's instance, the messages I sent are handled sequentially by my backend lex bot lambda. This is not the case if I were to open the website in 2 different browsers.

I'm suspecting this is may be due to how AWS Cognito authentication puts the userID within local storage or something within the lex-web-ui logic itself that's detecting and preventing the concurrent executions from the same user (sessionID) within the same browser but I'm not sure. Could some one provide some insight and potential ways I can get around it if it exists?

My issue is similar to what was asked here: #89

[israelias]

@yaodaniel Are you wanting sessionId/userId to be registered uniquely per IP address (browser agnostic aka "sequential") or per initialized conversation (per website aka "concurrent")?

[yaodaniel]

@yaodaniel Are you wanting sessionId/userId to be registered uniquely per IP address (browser agnostic aka "sequential") or per initialized conversation (per website aka "concurrent")?

Ideally what I'm looking for is per initialized conversation, such that a single person can open multiple tabs of my website which would instantiate multiple conversation instances and they can all be handled concurrently.