Any idea how long SETI is accepting v2.x client results?
- Thread starter Sukhoi
- Start date
> Is this for real this time? Will v1.x/2.x results simply be rejected or
> is there a way to detect the version number of the client hammering the
> ports and can workunit upload to them be prevented?
Yup. It's for real this time. When we released 2.x we didn't bother rejecting 1.x results since we believed that 3.x was around the corner. Making both 2.x and 3.x mandatory upgrades so close together would have bugged a lot of people, so we just let it slide.
As for the second question, we know the version of the clients sending results back, and we can easily have the server behave in one of three ways:
1) Accept the result and send a new workunit, no questions asked
2) Accept the result, have the client present a warning message saying there's a new client available for download, and then send a new workunit
3) Do not accept the result and have the client present a warning message saying there's a new client available for download and the current client won't work until you get it.
Right now we're at (1) for all versions. Soon, we'll make the server behave like (2) for all versions before 3.x. After the "grace period" the server will behave like (3) for all versions before 3.x.
All this logic has been working all along in the client and server, we just haven't implemented it since the days of 0.x
- Matt - SETI@home
> is there a way to detect the version number of the client hammering the
> ports and can workunit upload to them be prevented?
Yup. It's for real this time. When we released 2.x we didn't bother rejecting 1.x results since we believed that 3.x was around the corner. Making both 2.x and 3.x mandatory upgrades so close together would have bugged a lot of people, so we just let it slide.
As for the second question, we know the version of the clients sending results back, and we can easily have the server behave in one of three ways:
1) Accept the result and send a new workunit, no questions asked
2) Accept the result, have the client present a warning message saying there's a new client available for download, and then send a new workunit
3) Do not accept the result and have the client present a warning message saying there's a new client available for download and the current client won't work until you get it.
Right now we're at (1) for all versions. Soon, we'll make the server behave like (2) for all versions before 3.x. After the "grace period" the server will behave like (3) for all versions before 3.x.
All this logic has been working all along in the client and server, we just haven't implemented it since the days of 0.x
- Matt - SETI@home
From teamlambchop
The grace period will be several weeks after the "full-blown" official announcement, whenever that may happen. They are quietly letting things roll out right now, because they don't want the download servers to get too overloaded at the moment. We will have to see what kind of timescale this will be on...and I will let ya know when i find out.
The grace period will be several weeks after the "full-blown" official announcement, whenever that may happen. They are quietly letting things roll out right now, because they don't want the download servers to get too overloaded at the moment. We will have to see what kind of timescale this will be on...and I will let ya know when i find out.
oh man... that kinda sucks, since a lot of people will still use the betas (ie v2.70) to boost their stats. when v3.0 becomes mandatory we will all be on a level playing field.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 23K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 18K
-
-
-
Facebook
Twitter