home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!microsoft!hexnut!alistair
- From: alistair@microsoft.com (Alistair Banks)
- Subject: Re: Looking for rshd, telnetd, ftpd etc.
- Message-ID: <1992Sep04.011400.10545@microsoft.com>
- Date: 04 Sep 92 01:14:00 GMT
- Organization: Microsoft Corporation
- References: <1992Sep01.191707.28916@news.mentorg.com> <m0NgqB2w164w@underg.UUCP> <1992Sep2.142010.28953@csi.uottawa.ca>
- Lines: 28
-
- In article <1992Sep2.142010.28953@csi.uottawa.ca> duwors@csi.uottawa.ca (Robert J. Du Wors) writes:
- >
- >
- >I strongly suggest that remote login is a fundamental network primitive for
- >the construction of distributed (read "heterogenous" and "majority of")
- >applications.
-
- Please look longer and closer over Windows NT - one of its most imporant
- features is the inclusion and use of RPC. Remote access by terminals of
- character or graphic type does not constitue distributed processing. RPC
- seperates the location of the execution of code and its caller. If apps
- are built around RPC, then the location of the execution can be distributed
- around a number of seperate machines on a network. Indeed, a key focus of
- the Windows "Cairo" work is to allow instances of classes to execute at remote
- locations, as defined at runtime
-
- Remote login has absolutely nothing to do with distributed processing - it
- is a poor-man's way of starting remote tasks, by forcing the user to
- choose location through archaic means. Windows NT allows you to start
- remote tasks, at a given location
-
- Remote access is not itself without uses - when users wish to be guided
- through a task by a distant "helper", when a rude "overseer" wishes to
- spy-in on a subordinate worker, etc. These are niche special cases, but
- they're important, and they're well coverred by products in the Windows
- 3.x world, and I expect will be coverred by similar products for Windows NT
-
- -- Alistair
-