You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am hoping to use this library to write Go-based servers that can be accessed via other means than a TCP port, such as bidirectional pipes or even a serial port. If it's feasible, I can contribute the changes as PR. Is there some reason that I can't foresee why this wouldn't work? The client seems to be able to work with them.
The text was updated successfully, but these errors were encountered:
On Jul 30, 2018, at 7:15 PM, Chris McGee ***@***.***> wrote:
I am hoping to use this library to write Go-based servers that can be accessed via other means than a TCP port, such as bidirectional pipes or even a serial port. If it's feasible, I can contribute the changes as PR. Is there some reason that I can't foresee why this wouldn't work?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#38>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFdom2acjO5MqPMPsck8rFvBF_n9kZmuks5uL5N8gaJpZM4VnVMk>.
I am hoping to use this library to write Go-based servers that can be accessed via other means than a TCP port, such as bidirectional pipes or even a serial port. If it's feasible, I can contribute the changes as PR. Is there some reason that I can't foresee why this wouldn't work? The client seems to be able to work with them.
The text was updated successfully, but these errors were encountered: