> Okay, let's go through the process that's happening step by step.
That's nice to you. Sorry for the trouble.
> You point the browser at http://vncserver:5800/
OK.
> This connects to the VNC server (winvnc4.exe) which is pretending to be
> a web server.
Well, the notion of "pretending to be" is pretty vague to me...
Let me try to clarify that a bit.
When we point the browser at http://vncserver:5800/, we "talk" to a process
running on "vncserver" and listening on port 5800.
The process is not an HTTP server, right.
Yet it is capable of understanding and handling (some?) HTTP requests.
So the VNC team has implemented what is necessary to do so.
> The browser will issue an HTTP "GET /" request to which
> the VNC server will respond with the source you posted earlier.
OK.
> This will then cause the browser to request the vncviewer.jar file
(since
> it's needed for the embedded object).
Euhm, sorry..., what do you mean by "the embedded object"?
Do you mean:
a Java object executing its "main" method on the client
and which is sort of a "loop" waiting for events to occur?
> The VNC server will send this file (reading it directly from memory) to
> the browser.
OK.
> This is all the communication which is done over port 5800 - at this
> point the browser has all it needs to run the Java client.
> The browser now starts up its JRE (or Microsoft Java interpreter) and
> loads the various .class files from the vncviewer.jar archive. OK.
OK.
And, at that precise moment, pops up the dialog box I mentionned in my
first post, no? (The dialog box which title is "VNC viewer: Connection
details").
> The java application will then act as a normal VNC client, attaching
> to the VNC server on port 5900 and sending its RFB requests.
So, once this has been done, the 5800 port is not used anymore, is that so?
OK, so:
First:
a communication is established between:
- an HTTP client (the web browser) (I don't think it is precise enough, is
it?) and
- a process running on a server and listenning to port 5800
using the HTTP protocol (or a digest of it?).
This communication aims at downloading ".class" files which reside
on the server (in an ".exe" embedded ".jar" file) down to the HTTP client.
Second:
a second communication is established between:
- the HTTP client (same lack of precision as above) and
- a process running on the server and listenning on port 5900
using the RFB protocol (not sure this is precise either).
This communication is used for updating both the server
and the client "view" of the server as events occur.
> Hope that clears things up for you,
> Robin
>
> --
> ___
> ( ' } | Robin Hill <[EMAIL PROTECTED]> |
> / / ) | Little Jim says .... |
> // !! | "He fallen in de water !!" |
Thanks to you.
--
Leon
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
