We have an implementation plan for the attribute plugin. We plan to base it around the plugin.c so that it can be available for all files, directory or otherwise.
Every file which has a pseudo will gain a new user-attributes pseudofile. This pseudofile will essentially wrap a standard directory. In order to provide support for this directory, this plugin will include a new field on the inode which points to a standard dir_file. When a new file is created, this inode will be created as well, and when a file is deleted, this one must be removed (with children) as well. Future versions should provide the optimization of only creating the inode once it becomes needed and otherwise simulating an empty directory. Namesys folks, does this seem like a good course of action? -pvh -- Peter van Hardenberg ([EMAIL PROTECTED]) Victoria, BC, Canada
