home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.cell-relay
- Path: sparky!uunet!usc!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!netcomsv!iscnvx!news
- From: bantha.decnet.lockheed.com!young
- Subject: Today's Problem
- Message-ID: <1992Sep4.131447.18263@iscnvx.lmsc.lockheed.com>
- Reply-To: young@bantha.decnet.lockheed.com
- Sender: news@iscnvx.lmsc.lockheed.com (News)
- Organization: LMSC, Sunnyvale, California
- Date: Fri, 4 Sep 92 13:14:47 GMT
- Lines: 29
-
-
- Far into the future (mid 1993) server nomenclature is fading from
- our language, being replaced by server "waves" which migrate about
- the virtual path networks (enabled by wave interpreters at each node).
-
- The backup server, for instance, migrates in turn to each desktop,
- activates a local daemon to check for any files which need backup.
- Upon finding one or more, the backup wave then explores the local
- region for desktops with extra disk capacity. It then moves the files
- to a neighbor node, and moves on to the next desktop.
-
- Question:
- 1) How can we be sure that the backup wave touches every desktop in
- the enterprise?
-
- 2) What two things to we need in the wave interpreters to insure that
- a break in the network does not leave a wave protocol in an unstable
- state?
-
- Extra Credit:
-
- 3) Since the wave has no home, what constitutes its center? How do we
- define its current active region?
-
- 4) How many vci/vpi pairs does the wave use? Can all server waves use the
- same vci/vpi set?
- Matt Young
- Lockheed
- (408) 756-6789
-