Using the term "server" is very confusing in PCHW

[thoste]

The usage of the term "server" is very confusing in PcHelpWare's world.

In contrast to the remaining computer world teh server does NOT "serve" as a server but initiates the connection.

Whereever else a client-server architecture is working the client
is requesting services from the server !! Think of a java app which contacts the database server or a browser (=client) requests pages from the web server.

It took me a time to get used to this "special" view in PcHw scenarios.
I would urgently suggest to describe this "unusual" server role in big bold red letters at the top of the manual on page

http://www.uvnc.com/pchelpware/config/index.html

[mattice06082]

UltraVNC is based off RealVNC. A quote from the reference link http://www.realvnc.com/what.html,

It is remote control software which allows you to view and fully interact with one computer desktop (the "VNC server") using a simple program (the "VNC viewer") on another computer desktop anywhere on the Internet.

shows the origin of the terms "server" and "viewer". The server runs on the remote PC and the viewer is used to access the remote PC.

The terminology has been carried forward to PcHelpWare. Thus the individual providing remote assistance runs the viewer while the person receiving the remote assistance runs the server.

[jameshanley39]

I agree with the OP..


I agree with you, that is why I say Viewer and listener.. (of course , i'm not a developer or writing documentation)

You can have different meanings of client-server
e.g.
if you have a big network , with one central computer belonging to the IT manager.
And all the end users.
THe end users may run VNC servers.
The IT manager's comp runs the VNC client software, but it terms of centralization, it is the server and the end users are on the clients.

another thing.. as mentioned, their terminology comes from VNC. where the ffeature of reversing the connection, is presented as the server making a "reverse connection" to the client. Of course, i'm pretty sure there is no such thing.. And it is really that the program traditionally used to initiate connections, is able to listen. And the program traditionally listening, is able to initiate. I find it too confusing to use that terminology of client and server in that way.. it's nonsense. Notice they call the client the server, but they don't call the server the client. The way they use it without confusing themselves, is by saying that the server makes a reverse connection to the viewer.
For some reason they don't go all the way and call the viewer (which listens!) the client.. So they only mess up one of the words.. But as mentioned.. You can refer to server and veiwer and be sure to say "reverse connection" so you don't confuse yourself when talking of server connecting to viewer. And know that when you say X connects to Y, it implies that X initiates and Y listens. Just don't use the word server in terms of listening.. When you say server makes a reverse connection, the fact that it is connectin to something, implies it is not listening..
, amd the other thing, the thing it is connecting to, the viewer, is listening.
I doubt tha helps.. I find it confusing the terminology a nuisance myself.

But I know that the listening thing is on my machine / techie machine. (I am careful not to call it a server lest that terminology clash wit theirs)
And that listening program, can create another program (I won't call that server either.. but we agree it initiates).
And I know to send the idiot end user that initiating program..

I worked out how to use this program by messing around with it, not by reading any documentation.. i've found quite a few bits of software like that.. I just look to documentation for clues - not expecting explanations.. It's a helpful forum though.

[redge]

what is good name for you in short word ?

listener ? = pchelpware_viewer
initiator ? = pchelpware_server

[jameshanley39]

what is good name for you in short word ?

listener ? = pchelpware_viewer
initiator ? = pchelpware_server

I think it's important not to change the current terminology, or it would lead to more confusion..

Just be clear at the beginning of the document that the pchelpware server doesn't listen. The viewer listens. The server initiates connection to the viewer.. the server makes a reverse connection to the viewer.


That's just so they understand the terminology and concept of the document...

I think in those terms when reading documentation.. Really though, one works out how it works by using it.. But when using the program I know that as techie, I start the listening thing. And send them the file.


You might say in documenatation, in the case of for example.. A techie viewing an end users computer.. the techie runs the listener and sets the port forwarding, and sends the end user a file, which the end user runs and connects to the techie. The techie then sees the end user's screen.

If you were writing the documentation from scratch and had never used the word server the way you had.. I would have called the listener the server, and said that the client connects to the server, and the server views the client.