Look I'm pretty serious about the situation as it stands. If someone can just give me a little pointer to where the update client is implemented in the svn tree that would be great.
There is work to do here to integrate the update service into Apache's mirror infrastructure, and the division of labor between what the project can do and what infra needs to do isn't clear at all right now. It'd sure be nice to have a solution implemented prior to AOO 3.4's release, which I'm trying to accommodate but my time is limited. >________________________________ > From: Joe Schaefer <joe_schae...@yahoo.com> >To: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org> >Sent: Wednesday, March 28, 2012 10:33 AM >Subject: Info about the update protocol > > >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 > > > > > >
