I've only ever used it with wmii, but I've been looking for an excuse to write a Lua wrapper for it. :)
I think somebody was working on one in lua, but I don't know if they finished it.
If you write a Lua implementation or a lua wrapper for an existing C implementation let me know.
The walk function (which returns an iterator, successively returning tables with each file's stats in a directory) is not complete, it's terminating after the first file sometimes. I'll smooth that out once the server side of the library is together and testing can be self-contained.
I'd like to work on the server library sometime next week, but I'm pretty busy. Is there a better place to contact you with updates?
What do you think? In the mean time we can build some prototypes on different platforms.
The real reason why we don't know how and if this interaction model would work in practice - is the obvious absence of implementations.
A Lua client library for libixp should be pretty straightforward, looking at the source for ixpc. I might have that together this afternoon (particularly if my fiancee continues napping ;) ).
As for a server library, I'm still thinking about it, but passing an init function a table with callbacks for the various messages would be pretty straightforward - similar to LuaExpat's design (http://www.keplerproject.org/luaexpat/manual.html).
I'm silentbicycle on twitter, FWIW.
"ConcepOntoFs: A Semantic File System for Inferno", http://lsub.org/iwp9/cready/abheyshahplan9.pdf
this paper also has references to other papers on the topic.
This is why I over stress the need for use cases.
The reasoning behind this idea is how I use my files, the intuitive processes to organize and later find, the flow of thought and command.
"File indexing and searching for Plan 9", http://lsub.org/ls/export/tags.pdf describes mostly text indexing, but the interface to searching is through a file system (unfortunately not described in much detail at first glance).
only now do i remember that wrote something related once: attfs, http://www.ueber.net/code/r/attrfs. that's for inferno, using the styx/9p protocol. i never polished it, am not currently using it, and the interface the file system provides is not ready for casual file browsing, though that's mostly a detail (from an amount of code point of view). the things stored are strings though, not files. but the illusion that it stores files is easy to build.