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
socket.io instantiates the specified adapter, but does not wait for a callback that it is ready. This works fine for many scenarios, but not one where the adapter needs to spool up long-running processes where the adapter is not ready to do work until they are completed. Connections from clients are handled immediately, and if you use a simple pattern of emit-on-connect from client, an early client can easily connect prior to adapter readiness.
Expected behaviour
socket.io should pass a callback to the adapter constructor and wait for it to be called prior to continuing to stand up.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
You want to:
Current behaviour
socket.io instantiates the specified adapter, but does not wait for a callback that it is ready. This works fine for many scenarios, but not one where the adapter needs to spool up long-running processes where the adapter is not ready to do work until they are completed. Connections from clients are handled immediately, and if you use a simple pattern of emit-on-connect from client, an early client can easily connect prior to adapter readiness.
Expected behaviour
socket.io should pass a callback to the adapter constructor and wait for it to be called prior to continuing to stand up.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
This is particularly critical for the adapter I am developing that works with AWS SQS/SNS -- https://github.com/thinkalpha/socket.io-sqs
The text was updated successfully, but these errors were encountered: