Re: Virtual Filesystem

Quoting Alan Knowles <alan@akbkhome.com>: > class Horde_VFS_Object_file extends Horde_VFS_Object { I don't understand why you'd need to duplicate the backends. Why not just have Horde_VFS_File and Horde_VFS_Directory (or Folder, either way) classes, that wrapped the appropriate methods and stored internal references to a VFS backend instance? > If a new driver is written for the object one, then the Horde_VFS, > could provide a wrapper to it in a similar way... I see no reason to put backend code into the object drivers. You could even keep the API clean with a simple Horde_VFS_Object interface that wrapped a VFS backend instance in an object API, for any methods that the File and Directory objects mentioned above didn't cover. 3 classes, max, and you keep all the existing code and duplicate little to none of it... -chuck -- Charles Hagenbuch, <chuck@horde.org> "People ask me all the time what it will be like living without otters." - Google, thanks to Harpers