Hi, On Thu, Jun 17, 2004 at 00:38:12 +0200, Giulivo Navigante wrote:
On 06/16/04 21:57:35, Johannes Winkelmann wrote:
Sorry I didn't bring that up in IRC, but why do you switch away from httpup? I mean 'cvs update' transmits complete files as well (of course clients can request compression, but still), so it's similar in terms of netwerk load. I don't mean to advertise httpup, just interested in the reason your switching.
for base/opt collections we have to maintain the httpup REPO... the cvs wrapper does not require ftp/http space and overload to syncs is with the cvs tree. Well, both http space and network load are on the CLC server, right? We have httpup repositories anyway, so there's no additional load on your side. Even more, the CVS traffic will be on our side as well, so it basically boils down that we either offer ports to users using the httpup service we already have, or an additional, less secure [1] way (anonymous cvs) we had to implement anew. There's no visible difference to the user (besides the CVS directories in the ports tree when using the CVS service).
Or am I missing something fundamental here? Kind regards, Johannes References. 1. http://www.kb.cert.org/vuls/id/192038 -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net