Looking at the most recent experiment with
updates.services.apache.org does not inspire
my confidence that this service was well-thought-out
because it shouldn't be possible for j random user
to configure it to poll continuously for updates.
I can only hope that future variants of the service
were better designed from a network utility standpoint.

In any case is there any reason to suspect that throwing
this traffic at a protocol-compliant script will be able to
tell clients to back off?  Where is the update protocol
documented in case infra needs to write a more scalable
implementation of it as an Apache C module?  Any tips,
especially a willingness by volunteers to resolve outstanding
scaling issues, will be appreciated by both infra and your
users of the service.

TIA

Reply via email to