fuse/blackmatch: 'flatten' the fuse api implementation
authorrobk-tahoe <robk-tahoe@allmydata.com>
Thu, 16 Oct 2008 14:35:47 +0000 (07:35 -0700)
committerrobk-tahoe <robk-tahoe@allmydata.com>
Thu, 16 Oct 2008 14:35:47 +0000 (07:35 -0700)
commitc0b2aae0d49b2fbd2f07599da1fe7c4e35f0d1a1
tree7eb35e56ec45f66caa16ebe097f430b2dc1792a9
parent6a78000b55e4b59e6fa49041bd16766a1d84f545
fuse/blackmatch: 'flatten' the fuse api implementation

the previous revision of blackmatch used a file_class to delegate all fuse
api operations on files to a specific per-file class, which is an option
given by the python-fuse bindings.

this is a pre-cursor to the 'split' client/server version, which uses a
simple, moreover flat, rpc mechanism to broker access to methods.
contrib/fuse/impl_c/blackmatch.py