It seems like any solution is going to involve a client change. So what about my previous suggestion, namely a <no_partial_transfer> flag in the <file_info>. That would provide control at the server side, which is desirable. -- DPA
Carl Christensen wrote: > I don't think libcurl distinguishes between a 206 & 200 (from this message I > found from the main libcurl guy, although it's a two-year old thread): > > http://curl.haxx.se/mail/lib-2007-05/0011.html > > it seems safer to just not let curl try to compress/decompress (i.e. no gzip > in content headers) and treat it as any file (which can handle the resumable > downloads) and then just decompress by the app after the file is successfully > downloaded. > > Carl Christensen [email protected] http://www.geocities.com/carlgt1 > > > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
