|
From: | Peter Walter |
Subject: | [Gluster-devel] GlusterFS and cloud storage |
Date: | Wed, 08 May 2013 04:22:59 -0500 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 |
Now, why would I use vendor-specific FUSE drivers rather than just directly on the vendor API, and why do I need two FUSE abstraction layers? I understand that two FUSE abstraction layers would be much more inefficient than coding one layer to use the APIs of the vendors, but cloud drives are not speed demons anyway - and to add an additional API would not require a lot of interface glue, I think. In the alternative, I would have to consider the idiosyncrasies of every API, and some APIs are proprietary and/or unpublished. Since the vendor's drivers would have to conform to the published FUSE API, whatever their individual idiosyncrasies, the interface should be simpler.
Any comments or suggestions regarding this approach? Peter
[Prev in Thread] | Current Thread | [Next in Thread] |