Overview and motivation
This page discusses the low-level parts of the two wire protocols: ssh and http. The high-level parts (command set, arguments etc.) are not the scope of the unification.
Currently, handling the two wire protocols is almost entirely separate in the code; each has an adaption layer consisting of a function for each available command, which interacts with the common backend in the appropriate way. The two adaption layers are vaguely similar, but far from identical. Also, the feature set is different in the two underlying protocols. In particular, the ssh protocol is less flexible when it comes to argument handling. To sum up some observations about the current situation (not all of these are necessarily issues we should address):
- The ssh protocol is less flexible to extension than the http protocol.
- The transfer formats are dissimilar.
- The two adaption layers carry out a lot of the same work, but have little shared code.
In particular, the first point above means that we can't easily add optional arguments to the ssh protocol to enable feature extensions (such as light-weight copies), client capabilities and similar, whereas this is not a problem for http.
What we should do about it
We could proceed in a few phases as follows:
- Discuss a common feature set we want (and need) the low-level protocols to support, in order to ensure future flexibility and easy backwards compatibility.
- Discuss how this information should be transfered, and if we can somehow at this point (without breakage) make the two transfer formats more similar.
- Change the protocols so the common feature set is properly supported.
- Consider how the common feature set can be unified in the code, write the common layer for this and change the current adaptors to use it.