Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Re: Terminal across network

by perlcapt (Pilgrim)
on Oct 21, 2004 at 13:43 UTC ( #401158=note: print w/replies, xml ) Need Help??

in reply to Terminal across network

If I understand that A creates a process on B which is, in fact displayed on A: The display window is provided by the window server on 'A,' hence A is called the server. The process on 'B' that created the window is called the client process. Admittedly this sounds back-assward, but it is the view of the windowing system.

If, however, A creates a window on itself, and in the window it connects to B in order to run a process on B, then, from the window management point of view, A is both the server and client. From the application point of view, assuming that A's window connects to a server on B, A is the application client.

Messy, huh?

It is important to separate the windowing environment from the application environment IF THE APPLICATION IS NOT A WINDOW BASED APPLICATION. Once the distinction is made as to which is the server and which the client, then the appropriate client and server code can be written. -ben

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://401158]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (6)
As of 2018-06-22 05:59 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (121 votes). Check out past polls.