Hello all,
I've pushed an early version of rsync-rfc-conformance, with thanks to Dan Mestas for assistance and encouragement. This specification is sufficient to write a program that can have a protocol v32 conversation with rsync as client or server, with all optional features. There's the odd wobbly bit (I'm not convinced the xattr/ACL protocol conformance test is quite right yet, for example) but it does seem to work pretty well. It also handles protocols 27-31 for various definitions of 'handle'. I've really only tested it against 32 and 31, mostly 32. There are many ways this might potentially be useful, for example, it could be a source of a new category of test case just for wire protocol.
Best,
--
Dan Shearer
dan@shearer.org / https://shearer.org
Hello all,
I've pushed an early version of rsync-rfc-conformance, with thanks to Dan Mestas for assistance and encouragement. This specification is sufficient to write a program that can have a protocol v32 conversation with rsync as client or server, with all optional features. There's the odd wobbly bit (I'm not convinced the xattr/ACL protocol conformance test is quite right yet, for example) but it does seem to work pretty well. It also handles protocols 27-31 for various definitions of 'handle'. I've really only tested it against 32 and 31, mostly 32. There are many ways this might potentially be useful, for example, it could be a source of a new category of test case just for wire protocol.
Best,
--
Dan Shearer
dan@shearer.org / https://shearer.org