public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: xconq7@sources.redhat.com
Subject: Re: HW requirements
Date: Sun, 11 Jan 2004 20:05:00 -0000	[thread overview]
Message-ID: <200401112005.i0BK5pS29385@panix5.panix.com> (raw)
In-Reply-To: <767D5297-4461-11D8-910E-000393439120@saugus.net> (message from Feneric Brown on Sun, 11 Jan 2004 13:10:39 -0500)

> 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.

  reply	other threads:[~2004-01-11 20:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 18:10 Feneric Brown
2004-01-11 20:05 ` Jim Kingdon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-13 15:59 Eric W. Brown
2004-01-11 18:12 Eric W. Brown
2004-01-12 17:19 ` Eric McDonald
2004-01-11 16:52 Feneric Brown
2004-01-11 16:48 Feneric Brown
2004-01-11 17:02 ` Erik Jessen
2004-01-13 10:42   ` Bruno Boettcher
2004-01-10 17:57 New Action: change-type Hans Ronne
2004-01-10 18:59 ` HW requirements Erik Jessen
2004-01-10 19:44   ` Hans Ronne
2004-01-10 23:31     ` klaus schilling
2004-01-11  0:25       ` Erik Jessen
2004-01-11  3:44         ` Jim Kingdon
2004-01-11  7:25           ` Erik Jessen
2004-01-11  7:45             ` Eric McDonald
2004-01-11  7:52               ` Erik Jessen
2004-01-11 21:19               ` Jim Kingdon
2004-01-11  0:31       ` Hans Ronne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200401112005.i0BK5pS29385@panix5.panix.com \
    --to=kingdon@panix.com \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).