From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10628 invoked by alias); 11 Jan 2004 20:05:52 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 10621 invoked from network); 11 Jan 2004 20:05:52 -0000 Received: from unknown (HELO mail1.panix.com) (166.84.1.72) by sources.redhat.com with SMTP; 11 Jan 2004 20:05:52 -0000 Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id C874748809; Sun, 11 Jan 2004 15:05:51 -0500 (EST) Received: (from kingdon@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i0BK5pS29385; Sun, 11 Jan 2004 15:05:51 -0500 (EST) Date: Sun, 11 Jan 2004 20:05:00 -0000 Message-Id: <200401112005.i0BK5pS29385@panix5.panix.com> From: Jim Kingdon To: xconq7@sources.redhat.com In-reply-to: <767D5297-4461-11D8-910E-000393439120@saugus.net> (message from Feneric Brown on Sun, 11 Jan 2004 13:10:39 -0500) Subject: Re: HW requirements References: <767D5297-4461-11D8-910E-000393439120@saugus.net> X-SW-Source: 2004/txt/msg00063.txt.bz2 > Actually, as long as the host machine is beefy enough, the people > connected can play Cconq with much lesser clients. Just in case it was unclear to anyone on first reading, "client" and "host" here refer to remote login (say, via ssh or dial-up or whatever). The xconq protocol would presumably require roughly the same resources on the host machine or the joining machine, since they both keep a complete copy of the state and do all the calculations in parallel.