Open kumavis opened 11 years ago
But then again -- is this meaningful ? What role would filesystem-browserify play as a thin API layer? would it make more sense to just have a variety of direct fs-to-DB packages?
Here are some imagined architectures:
In all situations the direct line from app through filesystem-browserify makes me feel like it is an unnecessary layer. Though maybe it would provide utility via DRY and solving some gotchas. I suppose I need to have a good read-through of the code before making such grandiose statements ; )
Thoughts?
more detailed example stacks
This would require splitting this repo into 1) a thin virtual file system API 2) a filesystem-browserify-indexedDB adapter
This would provide the advantage of allowing users to utilize the virtual file system API to interact with a variety of DB flavors and DB-like interfaces.
Other possible FS adapters: -LevelDown via https://npmjs.org/package/level-js -Dropbox via the dropbox API