9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Edmondson davided@sco.com
Subject: local and remote cpu resources and the acme model of interaction
Date: Mon, 24 Apr 1995 05:00:08 -0400	[thread overview]
Message-ID: <19950424090008.opvk-vBj8AnX7aYN38c6pSLdpEYFDVvdau8zVC8p1zg@z> (raw)

something that i've been puzzling about over the weekend:  in the
original plan9 papers terminals are described as (my words) `a machine
which runs the window system and the editor'.  cpu servers are used
for compiling (and the like).  other people have noted that they run
mail notification programs on their terminals, and so it seems that
terminals are used to offload user interaction and possibly user
notification from the cpu servers, which are used for more
computationally intensive tasks.

now there is acme.  acme includes an editor, it is a window system,
and the mail component does notification.  if i hit `mk' in the right
place in acme it will (perhaps) cause the compiler to run.

where should acme be run ?  if i run it on the terminal, then i end up
compiling there.  if i run it on the cpu server, then the server is
doing a lot of the little jobs that the terminal was so good at.

perhaps, given the rising power of the terminals, this is now a moot
point - i would guess that an r4000 is capable of running the compiler
when necessary (even if it only has a relatively slow connection to
the fileserver), but then when would i use the cpu server ?  and,
perhaps more importantly, how does it fit into acme's model of
interaction ?

just the ramblings of an idle mind (whilst digging my garden as it
happens).

dave.






             reply	other threads:[~1995-04-24  9:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-04-24  9:00 Dave [this message]
1995-04-24 10:24 Gary
1995-04-24 11:11 Dave
1995-04-24 15:07 rob
1995-04-25  5:46 Matthew K
1995-04-25  9:37 Dave
1995-04-25 10:21 Gary
1995-04-25 14:49 Matthew K
1995-04-25 15:45 Alberto
1995-04-26 20:09 serge

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=19950424090008.opvk-vBj8AnX7aYN38c6pSLdpEYFDVvdau8zVC8p1zg@z \
    --to=9fans@9fans.net \
    /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 NNTP newsgroup(s).