Date: Wed, 07 Jul 2004 12:15:49 -0400 From: Vladimir Dyuzhev <vladimir-dozen@sympatico.ca> To: Maxime Henrion <mux@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Rewrite cvsup & portupgrade in C Message-ID: <40EC21B5.60509@sympatico.ca> In-Reply-To: <20040707153725.GH82302@elvis.mu.org> References: <E1Bhd1M-000KEo-Nz@smp500.sitetronics.com> <200407062323.02854.kirk@strauser.com> <20040707043251.GA35651@troutmask.apl.washington.edu> <200407062345.24117.kirk@strauser.com> <20040707070012.GC38356@dragon.nuxi.com> <40EC11EB.4060804@sympatico.ca> <20040707152149.GG82302@elvis.mu.org> <40EC17DC.9020307@sympatico.ca> <20040707153725.GH82302@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
ehlo. > Please go take a look at the CVSup webpage and click on the "Why is > CVSup so fast?" link. CVSup is far more than a "downloader" and the > way it is designed makes it inherently multi-threaded. It's of course > theoritically possible to write it single-threaded but it would be a > real nightmare, and it would also be rather stupid IMO. I like threads by myself. But looking on the description what that threads in CVSup do, I think it could be easely achieved with fork or finite state machine. I do not going to insist on it, though. Looking forward to see the csup in the *base* distribution. dozen http://dozen.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40EC21B5.60509>