Somehow, I knew this was coming. Now, you add a whole class of new problems: instead of one successful upload, you now need a number of smaller successful uploads, and you have to reassemble the chunks.
What happens if you split things into 20 chunks, and 19 make it to the server -- then the client disappears (failed drive, struck by lightning, etc.)? As with so many cases, you've not solved the problem you've moved it around. -- Lynn Martin wrote: > Lynn W. Taylor wrote: > [...] >> As for the fact that the full upload has to complete before the error >> comes back, that's as much an artifact of HTTP as anything else, and >> can't be fixed without using something other than HTTP. > > Include some mechanism to automatically break up large transfers into > smaller more manageable chunks?... > > A number of smaller chunks have a much better chance of success than one > very large lump if there any networking problems (congestion or otherwise). > > > Regards, > Martin > _______________________________________________ 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.
