[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

185.0. "DECwindows on CI" by MEMV02::TESTMIN () Mon Feb 13 1989 09:07

    A few people are requesting DECwindows to be installed on the main
    timesharing cluster.  My question is: what will it buy them?  How
    will they access it?  Can they use DFS from their VAXstation?  They
    certainly can't set host?  I guess they can use the development
    piece??
    
     Please enlighten me...
    
    Thanks

T.R Title User Personal
Name Date Lines

185.1 I buys them a lot of CPU capability they are now denied PRNSYS::LOMICKAJ Jeff Lomicka Mon Feb 13 1989 09:58 21

T.R	Title	User	Personal Name	Date	Lines
185.1	I buys them a lot of CPU capability they are now denied	PRNSYS::LOMICKAJ	Jeff Lomicka	`Mon Feb 13 1989 09:58`	21
	Well, actually, it buys them a LOT. You see, unlike VWS, DECWindows applications communicate to the workstation display using a network connection which is much like SET HOST. The difference is that instead of terminal-like commands, there are commands for manipulating windows and drawing things. By installing DECWindows on a system with lots of CPU, your users will be able to work more efficiently by running the programs on the big CPU, but with the workstation doing all of the Graphics. This is what is mean when we use the terms "client" and "server" with respect to DECWindows. To be a DECWindows server is to offer user interface and graphics services to an application. To do this, you must be a workstation with a screen, keyboard, and mouse. A "client" is an application program, and can run on any computer on the network, workstation or not. You should do as they ask, and watch what happens. You'll be amazed, I'm sure.

Well, actually, it buys them a LOT.

You see, unlike VWS, DECWindows applications communicate to the
workstation display using a network connection which is much like SET
HOST.  The difference is that instead of terminal-like commands, there
are commands for manipulating windows and drawing things.  By
installing DECWindows on a system with lots of CPU, your users will be
able to work more efficiently by running the programs on the big CPU,
but with the workstation doing all of the Graphics.

This is what is mean when we use the terms "client" and "server" with
respect to DECWindows.  To be a DECWindows server is to offer user
interface and graphics services to an application.  To do this, you must
be a workstation with a screen, keyboard, and mouse.  A "client" is an
application program, and can run on any computer on the network,
workstation or not.

You should do as they ask, and watch what happens.  You'll be amazed,
I'm sure.