Hi, I don't think so. It's been suggested/requested by many in the past - not sure if that ever happened.
As far as I know, the protocol is WebDAV, the server must support etags and should assume a certain etag generation/propagation model. For chunked upload there are custom header attributes used (oc-chunked or alike) and server should support that too. It would not be hard to find out what exactly goes on on the wire but I agree - it would be really good to be based on a stable spec of the protocol and data/consistency model. I think there could be enough people interested in this to pull together some effort maybe. kuba -- On Nov 30, 2013, at 9:13 PM, Bennett Todd <bennett.e.t...@gmail.com> wrote: > Is the protocol by which clients access the server, documented? > > Or has any alternative server been written? > _______________________________________________ > Owncloud mailing list > Owncloud@kde.org > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud