On 1 Sep 2005 07:47:00 GMT, jfh@green.home (John F Hall) wrote:

The second problem I see is that uploads and downloads seem to be aiming
at the same FQDN (setiboincdata...).  Surely there should be two FQDNs
for that.  That still would permit one sytem to be used if necessary -
they could resolve to the same IP address or to two address on the smae
computer if wanted - but would give more flexibility for tuning, to stop
uploads and downloads blocking one another.

In fact I would carry that further by using several FQDNs for each on a
round-robin basis.  That would have no effect normally, but would enable
access to be rationed during overloads by null-routing some of the access
attempts.

I hope that some BOINC developer will see this and give it - or
something similar - serious thought.

This may help you:
List-Archive: <http://ssl.berkeley.edu/pipermail/boinc_projects>
List-Post: <mailto:boinc_projects@ssl.berkeley.edu>
List-Help:
<mailto:boinc_projects-request@ssl.berkeley.edu?subject=help>
List-Subscribe:
<http://www.ssl.berkeley.edu/mailman/listinfo/boinc_projects>,

<mailto:boinc_projects-request@ssl.berkeley.edu?subject=subscribe>
It is the developers email group and the developers DO read it!