2015-12-21 15:17 GMT+01:00 Prashanth Pai <ppai@xxxxxxxxxx>: > The old code is still usable, just that it's based off an older version of Swift. We intend to revive this within a month. > And AFAICT, slower listing is the only draw back when compared to swiftonfile. So, waiting a couple of month would be the best choise, right ? I'm not in a rush, so I can wait a couple of month, if needed. > Not bad at all. gluster-swift would be a good fit for this use case. One point to note here that, neither swiftonfile nor gluster-swift does file locking during creation or access. > In other words, you won't run into any problems as long as multiple clients do not modify the same file at the same time. > For example, if a client is writing to file over FUSE and another client downloads the same file over HTTP, he may get half written content. This is expected. Ok. Are you aware of any company offering this kind hybrid storage? Just to know how they addressed these issues. _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
