leonardmh / saleaesockettransporthla Goto Github PK

Currently, implementers of ResponseHandler must respond either with None (which results in no response being sent) or a bytes object ready for transmission. This poses a problem with responders when they receive data that they have no intention of acting on.

The current best practice is to just respond with the same data that we received, but that is non-ideal for a lot of reasons.

A simple solution would be to implement a client-response message type which simply acknowledges that the message was received. The server would not be expected to act on that response.

This change should either be made in the UI or the README should be updated to remove it as it's a useless comment.

The FishResponder example is chuckle worthy and very simple to understand, but it's not a great practical example if you want to actually consume the data that is streamed out, process it, and then send packets back in to generate frames. A more realistic example would be helpful in getting started.