O/S hooks question

[Brandon Ibach]

Quoting James Wez Weatherall <jnw22 "at" cam.ac.uk>:
> >    If you can show me the place in the client code (preferrably the
> > X-windows version, as that's what I'm more familiar with, but the
> > Windows version will suffice) where it requests an update *other* than
> > in the two situations I mention, I shall be more than happy to admit
> > that I am wrong about this.
> 
> I'm afraid you are mistaken.  None of the available servers will transmit an
> update to a client unless it requests it - this is part of the protocol
> specification.
> 
   Yes, I agree that the protocol indicates that all updates should be
driven by the client.  And I realize, now, that I *was* mistaken about
the server sending an initial update without request.  My statement to
that effect was based on the apparent lack of such a request in the
X-windows viewer and the apparent scheduling of the update in the
WinVNC server.
   The trick with the viewer appears to be an X-windows-ism.  Upon
window creation, the X server sends an "expose" event to the viewer,
triggering the initial request for the whole screen.
   Not realizing how that worked, I assumed the server must be sending
that initial update on its own, so when I found the UpdateRect() call
in the client initialization code of the server, I figured it all made
sense.  My bad... :P
   On the plus side, at least I'm more familiar with the code, all
around, so it wasn't a totally futile argument, right? :)

-Brandon :)

PS- Tum, I tested your assertion by running a VNC session through a
quick and dirty netcat proxy, with logging.  Lo and behold, there was
the request!  I owe you 10 jellybeans. :)

---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------