Return result code from remote server? about smux

[WinstonPrivacy]

We researched this a little more. This seems to be fairly nuanced because smux drops packets that it doesn't understand.

So if you make a bad request and drop the entire session (as we were doing by accident), the next requests timeout because smux doesn't return anything.

Similarly, if you attempt to connect using a bad cipher, smux doesn't respond. This is probably ideal from a security standpoint though it can inconvenience callers.

This basically means that there needs to be an open smux tunnel between two peers for error messages to be exchanged. And if that's the case, the error messages can be sent at the application level (ie: HTTP).