Am 18.01.2010 um 18:25 schrieb Tarek Ziadé: > On Mon, Jan 18, 2010 at 5:27 PM, Jannis Leidel <jan...@leidel.info> wrote: >> Am 11.01.2010 um 22:22 schrieb Tarek Ziadé: >>>> Yup, nothing out of the ordinary... oh well, I guess it is just me and I'll >>>> wait and hope things get better ;-) >>> >>> If we have time at Pycon, and if some folks are interested, I would >>> like to finish the implementation of PEP 381, >> >> FWIW, I don't see the PEP to be completed. The actual mirror protocol, how >> to handle multiple (unsynchronized) indexes and the API design are clearly >> undecided -- and not discussed. > > If by "unsynchronized" you mean handling mutiple indexes one client > side that are not mirrors, that's not a protocol the PEP defines. > (even though it gives some info on it) > This is the business of the client software, and there's no API design > required for that in this PEP.
With "unsychronized" I mean indexes that are registered with PyPI to mirror it, but aren't up-to-date because of loss of connectivity/failure/interest. Will the mirrors check periodically the main index for updates? Or will PyPI send out a message to the slaves, requesting an update, e.g. with WebHooks [1] or PubSubHubbub [2]? Is this API going to be open for other non-official/non-open mirrors? > The PEP defines the mirroring protocol and the pages to be maintained > in a PyPI like server. Oh, you mean it will define it? Since there is just a placeholder on [3] :) Jannis 1: http://wiki.webhooks.org/ 2: http://en.wikipedia.org/wiki/PubSubHubbub 3: http://www.python.org/dev/peps/pep-0381/#the-mirroring-protocol _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
