[Noisebridge-discuss] Haschool

Jason Dusek jason.dusek at gmail.com
Sun May 10 01:15:06 UTC 2009


2009/05/09 Jeremy Fitzhardinge <jeremy at goop.org>:
> 2009/05/09 Jason Dusek wrote:
>>> your proposed project is quite similar to one I've been
>>> toying with (ie, thought about but not written a line of
>>> code), which is a not-completely-braindead fuse<->s3
>>> filesystem using the Haskell fuse and curl bindings.
>>
>> How do you think you'll handle the underlying eventual
>> consistency? This is an interesting problem with S3, in any
>> language.
>
> The existing fuse/s3 filesystems seem to basically ignore the
> problem.  If you 1) assume that there's nothing else
> concurrently changing the files and therefore 2) the s3
> filesystem always has up-to-date copies of recently written
> data, then it just needs to maintain a local cache until s3 is
> fully consistent with writes (ie, don't read back until the
> data is consistent).

  Which is when? I was not aware that Amazon published timings
  for that.

  Amazon's S3 does not have explicit versioning, though it does
  have ETags and timestamps. A sensible way to handle S3,
  actually, would be to version things yourself and then garbage
  collect older versions. That's not necessarily *required*
  though -- you have to weight that against the kind of safety
  you'd like to offer clients of your FUSE bindings. For my
  logs, the system you describe is fine; for my boss's
  Subversion repository, not so much.

--
Jason Dusek



More information about the Noisebridge-discuss mailing list