<HTML dir=ltr><HEAD><TITLE>Re: [Apt-zip-devel] Exporting USEMD5SUMS</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText87673 dir=ltr>
<DIV dir=ltr><FONT face=Tahoma size=2><B>De:</B> Eddy Petrișor<BR><B>Enviado el:</B> mar 18/03/2008 10:13<BR><B>Para:</B> Giacomo Catenazzi<BR><B>CC:</B> apt-zip-devel<B>Asunto:</B> Re: [Apt-zip-devel] Exporting USEMD5SUMS<BR></FONT><BR><FONT size=2>>>Yes, this sounds good. Still, the bottleneck here seems to be the server itslef. This would<BR>definitely have to be account (or some other authentication) based in order to prevent DoS attacks.<BR><BR>>Also, apt-zip would be only responsible of creating a "local machine status" snapshot (states of the<BR>packages+sources.list{,.d/*}).<BR><BR>>Still, I think this should *not* replace the current apt-zip-list and apt-zip-inst scripts until we<BR>have something really functional.<BR></FONT></DIV><FONT size=2></FONT></DIV>
<P><FONT size=2>To download, the server could generate an hmtl page with http:// links included to the mirrors with the packages </FONT></P>
<P><FONT size=2>So, downloading would be very easy: one could also use a spider for automatization.</FONT></P><FONT size=2>
<P><BR>>> Because the server will be in a debian machine, I think<BR>> coding it will be a lot simpler that actual apt-zip.<BR>> The only problem I see: resources. The apt is slow and<BR>> resource intensive (dependencies), and I've no idea<BR>> on bandwidth.<BR><BR>>It depends on which packages are downloaded. We could impose a soft limit of (say) 50MB for a<BR>apt-zip-server upgrade</P>
<P>Or include links to alternative mirrors (this could include links to debian mirrors ?).</P>
<P>Regards.</P>
<P>Pedro.</FONT></P></BODY></HTML>