Changes must affect ALL data structures, not just cache.

[dsoprea]

Changes must affect cache (as it currently does), as well as opened-files (OF), if necessary. Currently, local-originating changes will be taken of in the cache and opened-files from the remove() routine, and a subsequent Change will be received that will redundantly affect the cache. HOWEVER, if the change originates from another channel, such as the web interface or a sharing user, we'll find ourselves with an opened-file for an entry that is no longer officially cached (although the object will still exist due to a reference as an OF).

We should displace actual action code from the FUSE adapter into a separate class, and call that from the Change routine (the Change routines will no longer have a concept of what it's doing beyond calling the relevant handler, such as 'create', 'update', 'unlink', etc..).