From a77e818d9b4db8794b7a051118a0542de660a857 Mon Sep 17 00:00:00 2001 From: Constantin Kaplinsky Date: Thu, 5 Jun 2008 12:34:59 +0000 Subject: Removed support for continuous updates, a TightVNC-specific RFB protocol extension. That extension used to send framebuffer updates continuously, not waiting for clients' requests. However, it showed bad results with low-bandwidth connections, due to lack of proper data flow control. git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@2581 3789f03b-4d11-0410-bbf8-ca57d06f2519 --- common/rfb/SMsgReaderV3.cxx | 1 - 1 file changed, 1 deletion(-) (limited to 'common/rfb/SMsgReaderV3.cxx') diff --git a/common/rfb/SMsgReaderV3.cxx b/common/rfb/SMsgReaderV3.cxx index 468d74a0..37070a86 100644 --- a/common/rfb/SMsgReaderV3.cxx +++ b/common/rfb/SMsgReaderV3.cxx @@ -61,7 +61,6 @@ void SMsgReaderV3::readMsg() case msgTypeFileRenameRequest: case msgTypeFileDeleteRequest: handler->processFTMsg(msgType); break; - case msgTypeEnableContinuousUpdates: readEnableContinuousUpdates(); break; case msgTypeVideoRectangleSelection: readVideoRectangleSelection(); break; default: -- cgit v1.2.3