I thought that there was. It was just that the application uploaded it
instead of the BOINC client, or sent the final data to the server instead
of waiting for the client to do it. If this is true, it is a race to see
whether the file is uploaded or the work request is sent first.
For non-CPU intensive tasks, the report and the request should be in the
same packet.
jm7
Nicolás Alvarez
<nicolas.alvarez@
gmail.com> To
Sent by: [email protected]
boinc_dev-bounces cc
@ssl.berkeley.edu
Subject
Re: [boinc_dev] Multiple sched
09/14/2009 01:14 requests with no output files
PM
El Lunes 14 Sep 2009 09:49:57 [email protected] escribió:
> OK, is it clear on the front page of the website that the project needs a
> continuously on network connection?
>
> You can solve your problem by not marking the task as done until the
final
> communications with the server is completed. Then the report will be
> guaranteed to arrive after the upload.
What upload? There are no files to upload.
And that's not the point anyway. The problem is that BOINC is requesting
work
and then, in a separate request, reporting the task, even though the task
was
already ready to report. It could have done both things at once.
--
Nicolas
_______________________________________________
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.
