Comment by trashb

I may interpret this wrong, but the 9p protocol describes transfer protocol operations not data structure.

9p defines filesystem operations: attach, walk, open, create, read, write, clunk, remove, stat. And some additional handling operations: version, auth, error.

This project replaces those with RESTfull (CRUD?) operations. But this repository also seems to define what 9p does not, the structure of the data. It defines what files to write to and what to write to them. That seems outside of the 9p scope as you are defining the service behind the transfer protocol.

A RESTfull API to attach to a 9p backed does seem useful since the support for RESTfull API's is so huge. To me it's unclear how this monolithic approach is beneficial above a "RESTfull to 9p" proxy and a 9p service.