Ken,
I'm not very familiar with VNC other than to know that I want to get it and
try it out as soon as I have some time.
On Linux in particular and Unix in general (and even OpenVMS) programs
written for a graphical interface are written to use the services of an
X-server to render that interface. The bonus is that the protocols used to
communicate with the X-server work when the application (X-client) is on
the same machine as the server and they also work when the X-server and
X-client are on different machines or even totally different architectures.
So an X-client on a Linux machine can interact with a user at an X-server
on a Windows PC because the interface (protocol) doesn't change.
Dean O.
Ken Wilson wrote:
>
> Dean,
>
> What you say makes sense. Is it appropriate to say that the deal with
> VNC then is the implementation, that it uses the resources available on
> the Linux box and provides the end results to the client on the Windows
> box, thereby conserving resources on the Windows box at the expense of
> resources on the Linux box. One has to understand that VNC consists of
> two programs, a server and a client. My understanding now is that the
> thread is talking about a single program that would reside solely on the
> Windows box.
>
> Ken Wilson
> First Law of Optimization: The speed of a nonworking program is
> irrelevant
> (Steve Heller, 'Efficient C/C++ Programming')
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Dean Ostergaard
> > Sent: Friday, September 03, 1999 10:26 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [expert] Telneting to the server
> >
> >
> > It helps to think of the X server as the component that is
> > making graphics,
> > widgets, and other display and user interface services
> > available to the
> > client application which needs those services in order to get
> > input and
> > display output for the user.
> >
> > Client/Server has always referred to the components that
> > consumed (client)
> > and supplied (server) services never the physical location of those
> > components.
> >
> > The idea of a server being a box behind some locked door and
> > a client being
> > a machine on someone's desk is what happened after some suits
> > decided to
> > try and explain client/server to the more expensive suits.
> >
> > Dean O.
> >
> > Ken Wilson wrote:
> > >
> > > Interesting, not quite the way they taught us at college
> > but I'll have
> > > to take your word for it. The only package that we used was the VNC
> > > package, which was two part with the server portion running
> > on the Linux
> > > box. You had to telnet to the Linux box and start the VNC
> > server. It
> > > gave you a unique code and started running in the
> > background. You then
> > > logged off and started the VNC client on the Windows box,
> > giving it the
> > > code for accessing the VNC server on the Linux box.
> > >
> > > Ken Wilson
> > > First Law of Optimization: The speed of a nonworking program is
> > > irrelevant
> > > (Steve Heller, 'Efficient C/C++ Programming')
> > >
