On Fri, Apr 17, 2009 at 7:16 PM, Hugh Sasse <[email protected]> wrote: > On Fri, 17 Apr 2009, e deleflie wrote: > >> On Thu, Apr 16, 2009 at 8:54 PM, Hugh Sasse <[email protected]> wrote: >> > OK, I'd suggest that you explain what is broken about the headers, > > :-) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> > and we ask _why if he can roll out a fix on the raisin series for the >> > time being. We know he's frantically busy on all sorts of stuff, but >> > a new patched version of raisins would be nice. The Shoes news page >> > has been rather quiet over recent weeks, so it would let people know >> > things are still going on behind the scenes. >> >> That would be great... if the download header (OSX only) issue could > > You do need to say what it is now,
its been reported on this list before .... on OSX, this example does not work (error 401). http://gist.github.com/38170 > I don't know about this at all. There was some stuff about streaming > on Redhanded, but I think it was downloads, so.... Does S3 assume a > perfect, fast internet, or does it have another part of the API which > would allow you to split the file into chunks, so that when your dialup > connection falls over, or a passing train scatters your wireless connection > to smithereens, or,... you can still send the whole file eventually? S3 does not support incremental uploads. Its a pure HTTP post of a large file. But it works fine ... just as long as the software doesn't try and load 1GB files directly into memory and then post them out. That's what I mean by streaming ... its streaming off the hard disk.... read a bit, add it to the post, read a bit more, add it to the post.... etc. Etienne >> >> (I guess I should try it before asking the question) >> >> Etienne >> > Hugh
