Feature request - contacting server again in 67 minutes

patrik · 2006-09-23, 17:47

When an exponent finishes just after a full hour, say within two minutes, I get: "ERROR 23: Server busy [---] Will try contacting server again in 60 minutes." Then, after 60 minutes, it is again just after a full hour, and I get the same error message again. This can continue for a few hours.

It would be better if the delay wasn't exactly 60 minutes. I also think the delay should be greater than 60 minutes, since if we chose e.g. 58 minutes, the client could (under certain circumstances) hang a couple of minutes waiting for a timeout before giving up communicating.

Maybe it should be a prime number: 67 minutes?

Prime95 · 2006-09-23, 18:31

Go to Options / Preferences and change the network retry time to whatever you like. I'll make the default value something else next release

patrik · 2006-09-23, 18:47

Thanks. It never occurred to me that the network retry time also applied to other errors.

Andi47 · 2006-09-25, 06:37

Quote:

Originally Posted by patrik

When an exponent finishes just after a full hour, say within two minutes, I get: "ERROR 23: Server busy [---] Will try contacting server again in 60 minutes." Then, after 60 minutes, it is again just after a full hour, and I get the same error message again. This can continue for a few hours.

It would be better if the delay wasn't exactly 60 minutes. I also think the delay should be greater than 60 minutes, since if we chose e.g. 58 minutes, the client could (under certain circumstances) hang a couple of minutes waiting for a timeout before giving up communicating.

Maybe it should be a prime number: 67 minutes?

What about a Mersenne prime value like 31 minutes?

2006-09-23, 17:47	#1
patrik "Patrik Johansson" Aug 2002 Uppsala, Sweden 5²×17 Posts	Feature request - contacting server again in 67 minutes When an exponent finishes just after a full hour, say within two minutes, I get: "ERROR 23: Server busy [---] Will try contacting server again in 60 minutes." Then, after 60 minutes, it is again just after a full hour, and I get the same error message again. This can continue for a few hours. It would be better if the delay wasn't exactly 60 minutes. I also think the delay should be greater than 60 minutes, since if we chose e.g. 58 minutes, the client could (under certain circumstances) hang a couple of minutes waiting for a timeout before giving up communicating. Maybe it should be a prime number: 67 minutes? Last fiddled with by patrik on 2006-09-23 at 17:48

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Feature request	tcharron	Software	3	2018-10-03 20:08
feature request: P-1 file storage on server	tha	Software	13	2014-03-04 15:09
feature request P-1	tha	Software	4	2014-02-23 21:29
Feature request (Again)	JuanTutors	Software	7	2008-10-30 00:19
Feature Request	S3SJK	Software	10	2005-02-13 00:40

2006-09-23, 18:31	#2
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 17·487 Posts	Go to Options / Preferences and change the network retry time to whatever you like. I'll make the default value something else next release

2006-09-23, 18:47	#3
patrik "Patrik Johansson" Aug 2002 Uppsala, Sweden 5²·17 Posts	Thanks. It never occurred to me that the network retry time also applied to other errors.