Joined: 30 Jun 02
The client should wait at least 11 minutes every time between server queries to avoid the "not sending work" message, of course.
|ID: 3175 ·|
John McLeod VII|
Joined: 15 Jul 99
Actually, this should be sent from the server to the client as part of the transaction indicating that the server will not fullfill the request. This is because different projects have different policies on the minimum timeout value.
|ID: 3228 ·|
Joined: 10 Feb 01
Different projects may have different policies for the amount of time between server queries, but that doesn't change the fact that for some reason it desides all kinds of random times to try contacting the server, ranging from well less than a minute, to more than 4 hours and probably even days in some cases (although that I haven't seen). I don't have a problem with it telling the client to try back in 10 or more minutes, but it's not good for it to tell it to contact it in 8 minutes, and then goes and tells BOINC it contacted it too soon and it has to wait another 10 minutes. The server needs to be set so that when it does respond telling a client to wait, that it not give the client a time LESS than the minimum. It doesn't need to wait 11, just 10.
|ID: 3256 ·|
©2016 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.