Excuse me for assuming you were refering to the unix version.

I haven't developed under Windows for a looooong time (ver. 3.2 ;-) ) but I
would be willing to bet that a lot of your questions could be answered by
loading it into Microsoft Developer Studio and poking around.


Date:          13.12.2000 18:34
To:            [EMAIL PROTECTED]




Reply to:      [EMAIL PROTECTED]

Subject:       Re: Server documentation?
Message text:


Carlyle Sutphen wrote:
>
> It would probably be a good idea to start here: http://www.xfree86.org/

Sorry, perhaps my question wasn't clear.

I'm working with Server.cpp, which is part of AT&T's Win32 VNC 3.3.3
source code release. I would like to know how, within the code, the
server itself is started. How the server works with respect to the
clients (i.e., is the server a dormant process until AddClient() is
called?). Which method it is that actually "starts" the server (the
constructor?). What the socket methods actually do. There are a few
comments here and there within the code, but nothing very descriptive.

Is there additional documentation available, or perhaps one of the
developers can answer my question?

Thanks,
Laurel



--

Diese E-Mail enthdlt vertrauliche und/oder rechtlich gesch|tzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt|mlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie
diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorised
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to