Client/Protocol feature question

[Will Dean]

At 10:36 08/02/2000 +0000, you wrote:

>Good explanation, except that stage 5 doesn't really work that way. :)

:-) But Wez, you've got inside information about which bits I've worked on 
and which I haven't.   I should really have said:

5.  vncBuffer::GetChangedRegion does AddRects to the client's update region 
for some reason that I'm slightly hazy about and then something else that 
I'm a bit vague about happens afterwards.

>Stage 5 involves calling each client in turn to check whether it is waiting
>on an update.  If it is then the changed region check occurs.  It occurs for
>each client individually, which is inefficient for many clients but avoids
>checking when no-one wants an update - this could be improved for the
>multi-client case...

OK, I was talking rubbish!  I just listed everything done by the 
desktopthread.  I hadn't really appreciated that the region that 
GetChangedRegion adds to is the property of each client.

It does seem that the server could (if nConnectedClients > 0) keep a single 
dirty region and then just clip this against's the client's update request.

Cheers,

Will


--
Will Dean - Industrial Computing Ltd
Cambridge, UK


---------------------------------------------------------------------
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
---------------------------------------------------------------------