SpockFS – An HTTP-based network filesystem
1–10 of 14 posts
Re: SpockFS – An HTTP-based network filesystem
#2As a totally honest question, what about WebDAV is so bad that you'll never touch it and instead wen this route?
Re: SpockFS – An HTTP-based network filesystem
#3As a totally honest question, what about WebDAV is so bad that you'll never touch it and instead wen this route?
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a bit over-engineered, but the real problem (expecially when dealing with CardDAV and CalDAV) is the clients/servers inter-operation, as it looks like no-one is able to respect the RFCs (check the amount of hacks the radicale project or davvy needed to make OSX clients happy, or the differences between lightning, korganizer and so on). So the reason is that my patience ended :)
Re: SpockFS – An HTTP-based network filesystem
#4As a totally honest question, what about WebDAV is so bad that you'll never touch it and instead wen this route?
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a bit over-engineered, but the real problem (expecially when dealing with CardDAV and CalDAV) is the clients/servers inter-operation, as it looks like no-one is able to respect the RFCs (check the amount of hacks the radicale project or davvy needed to make OSX…
[deleted]
Re: SpockFS – An HTTP-based network filesystem
#5As a totally honest question, what about WebDAV is so bad that you'll never touch it and instead wen this route?
WebDAV doesn't go far enough; this exposes enough methods to provide a POSIX-compatible filesystem.
Re: SpockFS – An HTTP-based network filesystem
#6Earlier quoted context omitted.
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a bit over-engineered, but the real problem (expecially when dealing with CardDAV and CalDAV) is the clients/servers inter-operation, as it looks like no-one is able to respect the RFCs (check the amount of hacks the radicale project or davvy needed to make OSX…
[deleted]
lol :) but as already said there is no standard for POSIX access via HTTP. (WebDAV is not a competitor here, it is only the cause that pushed the development of spockfs)
Re: SpockFS – An HTTP-based network filesystem
#7As a totally honest question, what about WebDAV is so bad that you'll never touch it and instead wen this route?
Speaking from the perspective of someone who touched WebDav and then wrote my own server alternative. WebDav is really that bad. It has a special combination of using XML to be theoretically extensible while generalised to use the lowest common denominator of features.
I can't recall the specific details, but I certainly remember the pain. Apart from the inevitable and unnecessary translation from XML to a JavaScript object. I seem to recall there were weird cases where the XML format produced a different structure for cases where directories contained a single file.
In the short term I found capturing the output of "ls -al urlpath" was vastly easier to deal with.
In the longer term I wrote a server https://github.com/Lerc/userserv It might be worth me revisiting userserv to switch to the SpockFS protocol. Currently I use a websocket backchannel to do anything more complicated than static serving.
Re: SpockFS – An HTTP-based network filesystem
#8I really like that it gets along without XML. I don't like that it ends with a lot of new methods and headers.
Unrelated: Have you ever looked into the 9P protocol? I'd wonder if one can tunnel that through http, too.
Re: SpockFS – An HTTP-based network filesystem
#9Earlier quoted context omitted.
Seeing it from the perspective of a network filesystem (WebDAV by itself is a lot more, albeit afaik has never been used seriously as an authoring tool) it is a bit over-engineered, but the real problem (expecially when dealing with CardDAV and CalDAV) is the clients/servers inter-operation, as it looks like no-one is able to respect the RFCs (check the amount of hacks the radicale project or davvy needed to make OSX…
[deleted]
I'm wondering if Randall regrets writing this one because of the frequency it gets cited as a argument against new standards.
Almost every commonly used Standard was born in a world with existing standards purporting to be the ideal solution for that niche.
It's not even the sentiment that the comic represents. The comic refers to standards that try to in-the-darkness-bind-them.
Competing formats and protocols should be encouraged and should compete on merit. If people use them because they are good, _then_ they can be elevated to the status of a standard.
Bad formats only proliferate when they have another driving force behind them. "It's the standard" is one of those driving forces. Proprietary (and Cathedral) software also have the "We made this and you have to use it" problem.
Re: SpockFS – An HTTP-based network filesystem
#10I really like that it gets along without XML. I don't like that it ends with a lot of new methods and headers. Unrelated: Have you ever looked into the 9P protocol? I'd wonder if one can tunnel that through http, too.
POSIX has lot of methods, i did not found a more HTTP-compliant way to deal with it. If you have ideas feel free to expose them, i would be really happy to simplify the specs.
Regarding 9P, SpockFS is a fork of the 9spock project (unfortunately my company still did not released the sources, albeit the github repository is opened), and personally i think 9p is the currently best protocol available for sharing filesystems. Unfortunately the linux client is a bit weak as it does not manage disconnections/reconnections (once you lose the connection with the server you have to remount it)