Tahoe as git remote

[Greg Troxel]

Jean-Rene David <tahoe-dev at levelnine.net> writes:

> Actually the reason I wanted to use tahoe as a
> remote only was to avoid going the filesystem
> route. There is a protocol to talk to remotes and
> it's completely different (and hopefully simpler)
> than implementing a filesystem layer.
>
> What I didn't know, and found out while
> researching for this little project, is that git's
> remote protocol is clearly defined in its own man
> page and git even supports the addition of
> user-defined transports. I stumbled upon the
> gitremote-helpers man page and was very pleasantly
> surprised.

The problem with this approach is that for N users and M filesystems one
needs to write N*M adaptors.  This is why we have filesystem APIs and
why we have IP.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20151026/aab36e1a/attachment.pgp>