Jimmy Jia

It'd be sort of weird for types to have different names in Flow and TS, esp. if any of them are runtime types, no?

See also discussion in Django docs per https://docs.djangoproject.com/en/2.2/ref/models/fields/#field-options. It would feel weird to deal with this in e.g. SQLAlchemy, though, so some sort of unification of dealing with empty/null logic...

The motivation here is that we have some Socket.IO servers where we're not using any of the fallback methods, but where (for the moment) the abstraction offered by Socket.IO is...

How does this look?

Following up here. Is there anything I'm missing for this PR?

@invisibleroads Ping!

That's the idea. This brings things a bit closer to the logic on the Engine.IO JS client side, which doesn't special-case any of the transports on initial connect (it always...

Any updates here?

Ping.

Any update here? This has been sitting around for a while now. This is a use case that is present in the JS client, and is essentially required when not...