summaryrefslogtreecommitdiffstats
path: root/common/rfb/SConnection.cxx
diff options
context:
space:
mode:
authorConstantin Kaplinsky <const@tightvnc.com>2008-06-05 12:34:59 +0000
committerConstantin Kaplinsky <const@tightvnc.com>2008-06-05 12:34:59 +0000
commita77e818d9b4db8794b7a051118a0542de660a857 (patch)
tree5b065169be59eee819557cf6357beb1ccd79f236 /common/rfb/SConnection.cxx
parent67ebf00acc436b3bd8bcd9615d8b8610b91b0f09 (diff)
downloadtigervnc-a77e818d9b4db8794b7a051118a0542de660a857.tar.gz
tigervnc-a77e818d9b4db8794b7a051118a0542de660a857.zip
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
Diffstat (limited to 'common/rfb/SConnection.cxx')
-rw-r--r--common/rfb/SConnection.cxx7
1 files changed, 0 insertions, 7 deletions
diff --git a/common/rfb/SConnection.cxx b/common/rfb/SConnection.cxx
index 2fde9fbb..a61627ca 100644
--- a/common/rfb/SConnection.cxx
+++ b/common/rfb/SConnection.cxx
@@ -445,11 +445,6 @@ void SConnection::sendInteractionCaps()
scaps.addTightExt(msgTypeFileLastRequestFailed, "FTS_RQFL");
*/
- // Continuous updates:
- /* FIXME: EndOfContinuousUpdates message is not supported yet:
- scaps.addTightExt(msgTypeEndOfContinuousUpdates, "CUS_EOCU");
- */
-
//
// Advertise support for non-standard client-to-server messages
//
@@ -470,8 +465,6 @@ void SConnection::sendInteractionCaps()
ccaps.addTightExt(msgTypeFileDeleteRequest, "FTC_RMRQ");
*/
- ccaps.addTightExt(msgTypeEnableContinuousUpdates, "CUC_ENCU");
-
if (m_videoSelectionEnabled) {
ccaps.addTightExt(msgTypeVideoRectangleSelection, "VRECTSEL");
}