It shouldn't affect flow control. The callback will be called with an error, indicating incorrect usage of the Connection object. Internally, we don't call connect unless we are not already connecting. This statement should only cause the state of the connection to not be corrupted for the first call to connect, which was valid, as a result of improper calls to connect while a connect is in progress.

On Aug 27, 2013, at 3:40 PM, Robert Chiniquy <notifications@github.com> wrote:

> In lib/driver.js:
> 
> > @@ -291,6 +292,11 @@ Connection.prototype.connect = function(callback) {
> >        callbackWrapper = function(err) {
> >          if (!cbAlreadyReturned) {
> >            cbAlreadyReturned = true;
> > +          if (err && err.message === 'Already connecting') {
> Not a huge fan of flow control based on err.message but won't -1 for this
> 
> —
> Reply to this email directly or view it on GitHub.