Actually, the DDoS problem can come from any activity. Across several BOINC versions, scheduler hits have been tuned to the point that most clients touch the scheduler once per day.
The upload change is in the same spirit as the scheduler change (it also parallels a suggestion in RFC-2821, dealing with mail servers exchanging mail -- it says if "A" can't connect to "B" that "A" does not have to actually try to connect for every message queued to "B" -- it can remember for awhile). Ultimately, I think a project needs to be able to broadcast adjustments and have the client match. -- Lynn erbenton wrote: > Why is it that if a bunch of WU's are "Ready to Report" but not on the > transfer page > that they can upload so easily in one pass vs any WU's on the transfer > page may need many > attempts each before a successful upload of just 1 WU. Why doesnt the > Transfer Tab upload > everything there in one transfer like the "Project Update" seems to > accomplish > Better yet, get rid of the transfer tab altogether and just use Project > Update to upload whatever is > "Ready To Report", if a "Project Update" fails, just keep all like it is > - "Ready to Report" and retry > later. Your DDOS problems come from millions of upload requests to > upload *1* WU each from the > transfer page. > Eric > > _______________________________________________ > 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. > _______________________________________________ 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.
