sciencewhiz
Diamond Member
From Bovine's latest plan:
<< As it turns out, OGR25 is also approaching the time where we need to
manually reissue the remaining unreturned stubs necessary to complete both
of its first and second passes. We've decided not to begin issuing OGR26
merely so that we can focus more intently on getting the existing OGR24
and OGR25 stub spaces fully finished off. Because of this, we'll be
reducing the release rate of new OGR stubs (OGR24 and OGR25) into the
system so that we can give those outstanding stubs as much time as possible
to be handed in by themselves. Since the outgoing availability of OGR
stubs will now be much less, you may find that your client may return to
working on the RC5 project.
>>
This means is that if you have any clients with the project prioritity for rc5 set to 0 , they will stop working if there aren't any stubs availible.
It is unescesary to disable RC5. You will continue to work on OGR until the buffers run out and then you will switch to RC5. To make sure you don't switch to RC5 too often, use either a dialup detection option or a frequent buffer level checking option to ensure that OGR work is uploaded and downloaded before the client would normally start working on RC5. This way, even if you can't get OGR blocks, your client will crack RC5 instead of doing nothing.
edit: tried to clarify a few things (I wrote this to late last night)
edit2: clarified things more per jon's suggestion
<< As it turns out, OGR25 is also approaching the time where we need to
manually reissue the remaining unreturned stubs necessary to complete both
of its first and second passes. We've decided not to begin issuing OGR26
merely so that we can focus more intently on getting the existing OGR24
and OGR25 stub spaces fully finished off. Because of this, we'll be
reducing the release rate of new OGR stubs (OGR24 and OGR25) into the
system so that we can give those outstanding stubs as much time as possible
to be handed in by themselves. Since the outgoing availability of OGR
stubs will now be much less, you may find that your client may return to
working on the RC5 project.
>>
This means is that if you have any clients with the project prioritity for rc5 set to 0 , they will stop working if there aren't any stubs availible.
It is unescesary to disable RC5. You will continue to work on OGR until the buffers run out and then you will switch to RC5. To make sure you don't switch to RC5 too often, use either a dialup detection option or a frequent buffer level checking option to ensure that OGR work is uploaded and downloaded before the client would normally start working on RC5. This way, even if you can't get OGR blocks, your client will crack RC5 instead of doing nothing.
edit: tried to clarify a few things (I wrote this to late last night)
edit2: clarified things more per jon's suggestion
