Re: Checkout without storing two copies

> * HTTP(S) based sync protocol.

Mine uses Subversions WebDAV as is.

> * All files, both on the client and the server, are stored as plain files
with there original names.

Mine too, or plain binary 'as is'

> * Stores limited version history on the server only. Has limited support
for file versioning.

Mine: Only current version is stored on the client. Works out if 'clash' is
about to happen.

> * No web/graphical UI Designed to perform a single function only,
provides a minimal command line interface.

Yup, though I'll have a tray piece in time like
https://www.sparkleshare.org/ and DropBox.

> * No database dependency Stores file manifest information as regular
JSON.

I've metadata stored client side in JSON too.

> * Atomic file system operations through journaling.

I've no server side beyond Subversion.

* Supports partial checkouts

Got that too :)

For your README, you'd be better to move the rationale to a separate page,
and concentrate on hooking the potential user in.

- Paul
Received on 2017-09-27 19:14:48 CEST