Split protocol and local into separate crates
chipsenkbeil opened this issue · 2 comments
chipsenkbeil commented
The protocol section of distant-core
is starting to get polluted with implementation details for the local implementation of the API.
To reduce how many dependencies are being brought in and to separate logic to proper places, distant should be split out into these crates:
distant-auth
- authentication traits and implementation split by featuredistant-net
- network implementation (fine as is).distant-protocol
- data structures used for requests & responses related to distant.distant-core
- provides the glue and API traits to be implemented for supporting a distant client and server. Depends ondistant-net
anddistant-protocol
.distant-ssh2
- ssh2 implementation of distant. Depends ondistant-core
(and indirectlydistant-protocol
anddistant-net
).distant-local
- local implementation of distant (operates on local machine). Depends ondistant-core
(and indirectlydistant-protocol
anddistant-net
).distant
- CLI wrapper arounddistant-local
and optionallydistant-ssh2
.
chipsenkbeil commented
github-actions commented
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.