nonameentername / wmii

Automatically exported from code.google.com/p/wmii
MIT License
0 stars 0 forks source link

feature: replace IXP with simple key/value store #248

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Why all the complexity of 9P2000 and filesystem abstractions (obtain fid, walk 
tree, etc.) when wmii's state could be exposed via simple key/value store over 
a pipe or UNIX domain socket?

# creates (if needed) and updates a "foo" file in the rbar
PUT /rbar/foo
...content...
EOF

# deletes an existing "foo" file in the rbar
DEL /rbar/foo

# fetches the content of an existing "foo" file in the rbar
GET /rbar/foo

# fetches the list of sub-keys beneath "/rbar"
DIR /rbar

# fetches all keys in the system
DIR

What do you think?

Original issue reported on code.google.com by sunaku on 3 Jan 2012 at 7:56

GoogleCodeExporter commented 8 years ago
 Obviously the complexity is there so that it is possible to mount the filesystem and interact with wmii using standard file operations. It's not wmii anymore if you change the API so completely.

-sqweek

Original comment by sqw...@gmail.com on 2 Jul 2012 at 5:03