This PR does a lot of things. It adds support for sending and receiving messages. It also lets users wait for messages and have them printed as they come in. To support this, I had to re-engineer part of the backend, since most of the code assumed that one command=one response. I'm not sure that the way that I have done it is the best, but I think that we can see if it works and rework it later if we find out that the implementation is unworkable.
Since this PR introduces support for multiple responses to a message, we can probably implement other features that would get use from multiple responses, for example configuring noise gate thresholds (#65).
This PR does a lot of things. It adds support for sending and receiving messages. It also lets users wait for messages and have them printed as they come in. To support this, I had to re-engineer part of the backend, since most of the code assumed that one command=one response. I'm not sure that the way that I have done it is the best, but I think that we can see if it works and rework it later if we find out that the implementation is unworkable.
Since this PR introduces support for multiple responses to a message, we can probably implement other features that would get use from multiple responses, for example configuring noise gate thresholds (#65).