Article View: comp.sys.next.sysadmin
Article #1456Re: NXHost, Mach Ports
From: Stuart Ritchie
Date: Tue, 13 Oct 1992 00:18
Date: Tue, 13 Oct 1992 00:18
19 lines
1315 bytes
1315 bytes
gsk@world.std.com (Geoffrey S Knauth) writes: >Aha. Now I get you. Several months ago, Ray Bloom <ray@marble.com> >came up with the same solution you did. This solution is required any >time MACH PORTS are involved. Information presented to Mach Ports >circulates via en0, the single ethernet interface on a NeXT computer. >Mach Port data doesn't route. Does this mean that Mach IPC across the ISDN interface faces this problem as well? How does NXHost over 64kbps look like? Here's a thought... Currently, an app's connection to the window server requires good bandwidth and low latency. Now suppose that in "4.0" the app's UI code is separated from the app's brain. Then perhaps you might run the UI code locally and the brain on a remote machine. How would the channel requirements change? Stuart
Technical Details
Message-ID:
<1bd4ktINNqn5@stephen.cs.ubc.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!destroyer!cs.ubc.ca!stephen.cs.ubc.ca!not-for-mailReferences:
<Bvy9vq.6s4@world.std.com> <BvyM8w.Iqy.2@cs.cmu.edu> <Bw0Cxt.6ur@world.std.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!destroyer!cs.ubc.ca!stephen.cs.ubc.ca!not-for-mail From: sritchie@cs.ubc.ca (Stuart Ritchie) Newsgroups: comp.sys.next.sysadmin Subject: Re: NXHost, Mach Ports Date: 12 Oct 1992 17:18:37 -0700 Organization: Computer Science, University of B.C., Vancouver, B.C., Canada Lines: 19 Message-ID: <1bd4ktINNqn5@stephen.cs.ubc.ca> References: <Bvy9vq.6s4@world.std.com> <BvyM8w.Iqy.2@cs.cmu.edu> <Bw0Cxt.6ur@world.std.com> NNTP-Posting-Host: stephen.cs.ubc.ca