| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Just a basic question....
After hearing a DECwindows presentation yesterday, the presenter
stated that a VMS machine running DECwindows uses DECnet as the
transport medium. That is for a VMS server, accessing other clients,
uses DECnet to transport the X11 protocol. If that is so then how
can the VMS server access other clients other than DECnet based machines
eg. HP, SUN etc.
Thus the question is: Is it true that DECwindows uses DECnet as
a means of communicating between machines. And if so, are their
any plans or standards in the pipeline to address this problem.
James
Whose_not_an_expert_in_DECwindows.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 190.1 | PS to previous note | TRUCKS::BOOTH | James Booth CSS dtn.782-2091 | Tue Feb 14 1989 05:42 | 8 |
PS to previous note.
The presenter could not confirm this question, he was only presenting
in parrot fashion ( using others materials ) and not as an expert.
James
| |||||
| 190.2 | Just your basic answer | SDSVAX::SWEENEY | Roads? Where we're going we don't need..roads | Tue Feb 14 1989 08:20 | 26 |
With a little use of DIRECTORY/TITLE="TCP" or some other string you'll
find discussion of this _in_depth_.
I'll offer a summary as I present it (without a discussion of
futures)... Part of DECwindows is an implementation of the MIT X
Window System. The wise people at MIT decided to describe a set of
facilities for transport, not specify an implementation of them.
Therefore X "just calls" routines and has no need to know the specifics
of the transport. The method of transport is specified in the call to
XOpenDisplay, and syntax is defined there for DECnet, TCP/IP, and UNIX
sockets.
DECwindows version 1 represents a set of tradeoffs to achieve an
industry breaktrough in providing enterprise-wide integration. That's
not marketing fluff but reality. No one has anything quite like it.
There's no need to apologize.
For VMS, DECnet is supported. For ULTRIX, DECnet and TCP are
supported. Through the CONNECTION product these networks can be
conbined. For VMS, product managers are aware and they always looking
for feedback from the field that will help prioritize what VMS needs.
(As a side issue, third party implementations of DECNET do exist. And
the corporation is trying to align large networks with OSI eventually.
By that's a rathole for another conference.)
| |||||
| 190.3 | Just a basic thanks | TRUCKS::BOOTH | James Booth CSS dtn.782-2091 | Tue Feb 14 1989 08:57 | 15 |
Thanks for the answer. I think that the slides in the presentation
were a little bit misleading, they showed a network of VMS, Ultrix,
MS-DOS and other vendors machines. This on its own wasn't too bad
but the way it was drawn implied that the VMS machine could access
the "other vendors" machines. With the slide there was no mention
of gateways etc.
It only goes to show that it can be dangerous to present something,
without good knowledge, using other peoples material.
Thanks again
James
| |||||
| 190.4 | found this out at DECUS years ago... | MOVIES::LESLIE | Andy ��� Leslie | Tue Feb 14 1989 09:22 | 3 |
Yet another good example of why using parrots to do presentations is a
bad idea.
| |||||