mirror of
https://github.com/falk-werner/webfuse
synced 2024-10-27 20:34:10 +00:00
remove section about webfuse legacy
This commit is contained in:
parent
5805337981
commit
2829465d7c
12
README.md
12
README.md
@ -61,15 +61,3 @@ Unlike webfuse, davfs2 mounts a remote filesystem locally, that is provided by a
|
||||
- [Webfuse provider command line options](doc/webfuse_provider.md)
|
||||
- [Webfuse Protocol](doc/protocol.md)
|
||||
- [Authentication](doc/authentication.md)
|
||||
|
||||
## webfuse legacy
|
||||
|
||||
`webfuse2` is a complete re-implementation of the original idea behind `webfuse`. In contrast to the original `webfuse` implementation, `webfuse2` provides also write access to the filesystem and allows to use all standard options of a fuse filesystem.
|
||||
|
||||
But `webfuse2` marks also some breaking changes:
|
||||
|
||||
- `webfuse2` uses a new, binary protocol which is not compatible to the JSON-based protocol of legacy `webfuse`
|
||||
- `webfuse` does not provide an API nor a library to program against
|
||||
_(if you are interested in an API or a library for webfuse2 feel free to create an issue)_
|
||||
|
||||
When you are interested in the original `webfuse` implementation take a look at this [branch](https://github.com/falk-werner/webfuse/tree/webfuse-legacy).
|
||||
|
Loading…
Reference in New Issue
Block a user