From: Antonio SJ M. <tra...@sp...> - 2016-02-02 22:15:05
|
Moving from github[0]: Something has to be able tie together the requests. Keep state. That primary identifier or flow which ties together request A to B. That identifier may be used by the kernel but the file handle is not used by the kernel. So it's not clear why it was decided, besides convenience, to include a userland layer piece of data in the kernel <-> userland protocol. Keeping state in the message flow is nice and mostly stateless but in this case makes it a protocol change to allow the flexibility I was looking for. [0] https://github.com/libfuse/libfuse/issues/3#issuecomment-178805682 On Tue, Feb 2, 2016 at 3:29 PM, Nikolaus Rath <not...@gi...> wrote: > (let's continue this discussion on the fuse-devel mailing list please) > > — > Reply to this email directly or view it on GitHub > <https://github.com/libfuse/libfuse/issues/3#issuecomment-178805920>. > |