Andrew Kutta

``` Faye outgoing {"channel":"/meta/connect","clientId":"6p13gpcil0mrn281li95v1kqac7r","connectionType":"long-polling","id":"87"} Faye incoming {"channel":"/meta/disconnect","successful":true} Faye incoming {"clientId":"6p13gpcil0mrn281li95v1kqac7r","advice":{"interval":0,"reconnect":"none"},"channel":"/meta/connect","id":"87","error":"403::Unknown client","successful":false} ``` This is logged by adding an extension to the FayeClient: ``` const Logger = { incoming: function(message, callback)...

```449 Faye incoming {"clientId":"2v1ozicqq5hbjy11wiv2c7puqxf7","channel":"/meta/connect","id":"5m","successful":true} 450 Faye outgoing {"channel":"/meta/connect","clientId":"2v1ozicqq5hbjy11wiv2c7puqxf7","connectionType":"long-polling","id":"5n"} 451 Faye incoming {"clientId":"2v1ozicqq5hbjy11wiv2c7puqxf7","channel":"/meta/connect","id":"5n","successful":true} 452 Faye outgoing {"channel":"/meta/connect","clientId":"2v1ozicqq5hbjy11wiv2c7puqxf7","connectionType":"long-polling","id":"5o"} 452 Faye outgoing {"channel":"/meta/connect","clientId":"2v1ozicqq5hbjy11wiv2c7puqxf7","connectionType":"long-polling","id":"5o"} 453 Faye incoming {"advice":{"interval":0,"reconnect":"handshake"},"channel":"/meta/connect","id":"5o","error":"403::Unknown client","successful":false} 454 Faye outgoing {"channel":"/meta/handshake","version":"1.0","supportedConnectionTypes":["in-process","websocket","long-polling"],"id":"5p"} 455...

Currently 1.2.3 is running in my app, with a current release of 1.2.4 available. It does not seem to address this kind of bug. My guess at this point, is...

this is how i intercepted the disconnect event and pass it up to our implementation. It's not an ideal solution, I think this is actually an issue with Faye not...

My error handler just logs in again (probably unnecessary) and then starts a new streaming connection: ```javascript var str = this._org.stream({ topic: topic, oauth: oauth }); ``` I feel like...

I havn't changed the defaults, but I saw that the Faye client defaults were still setup properly while debugging in other portions of the client.

I could see scenarios where dead-letters are useful; however, I'd like to see it configurable. When using the Elastic sink ( #10839 ) we recently ran into an issue where...