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
Currently, you run one command at a time via distant send. Support for not closing the connection after one command would be ideal to avoid the cost of producing shared secrets for encryption, which can be expensive.
Fortunately, with the current design of the program, there is already an id associated with messages to distinguish themselves AND a process id included with all stdout/stderr. So keeping track of responses should be doable (via JSON).
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Currently, you run one command at a time via
distant send
. Support for not closing the connection after one command would be ideal to avoid the cost of producing shared secrets for encryption, which can be expensive.Fortunately, with the current design of the program, there is already an id associated with messages to distinguish themselves AND a process id included with all stdout/stderr. So keeping track of responses should be doable (via JSON).
The text was updated successfully, but these errors were encountered: