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

1 files changed, 0 insertions, 8 deletions

diff --git a/common/rfb/VNCSConnectionST.h b/common/rfb/VNCSConnectionST.h
index a388873d..cde2b31f 100644
--- a/common/rfb/VNCSConnectionST.h
+++ b/common/rfb/VNCSConnectionST.h
@@ -130,9 +130,6 @@ namespace rfb {
     virtual void setInitialColourMap();
     virtual void supportsLocalCursor();
 
-    virtual void enableContinuousUpdates(const Rect& r);
-    virtual void disableContinuousUpdates();
-
     // setAccessRights() allows a security package to limit the access rights
     // of a VNCSConnectioST to the server.  These access rights are applied
     // such that the actual rights granted are the minimum of the server's
@@ -154,8 +151,6 @@ namespace rfb {
     void setCursor();
     void setSocketTimeouts();
 
-    void resetRequestedRegion();
-
     network::Socket* sock;
     CharArray peerEndpoint;
     VNCServerST* server;
@@ -165,9 +160,6 @@ namespace rfb {
     bool drawRenderedCursor, removeRenderedCursor;
     Rect renderedCursorRect;
 
-    bool autoUpdatesActive;       // continuous updates enabled
-    Rect autoUpdatedRect;         // continuously updated area
-
     std::set<rdr::U32> pressedKeys;
 
     time_t lastEventTime;