diff options
| author | Pierre Ossman <ossman@cendio.se> | 2016-04-29 14:26:05 +0200 |
|---|---|---|
| committer | Pierre Ossman <ossman@cendio.se> | 2016-04-29 14:26:05 +0200 |
| commit | d408ca514655b4fe6e477680f22c4387b52446a6 (patch) | |
| tree | 9d512d443bdeeadd486f978889bdcd77374f7caf /win | |
| parent | c6df31db54bffe76ee5506a79f42cc7de7c541c3 (diff) | |
| download | tigervnc-d408ca514655b4fe6e477680f22c4387b52446a6.tar.gz tigervnc-d408ca514655b4fe6e477680f22c4387b52446a6.zip | |
Move socket write event handling in to the RFB core
What to do when a socket is writeable should be handled in the
RFB core code as there may be other events we want to fire off
when this happens.
Diffstat (limited to 'win')
| -rw-r--r-- | win/rfb_win32/SocketManager.cxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/win/rfb_win32/SocketManager.cxx b/win/rfb_win32/SocketManager.cxx index b073b8fb..5b211a0d 100644 --- a/win/rfb_win32/SocketManager.cxx +++ b/win/rfb_win32/SocketManager.cxx @@ -193,7 +193,7 @@ void SocketManager::processEvent(HANDLE event) { WSAResetEvent(event); // Call the socket server to process the event - ci.server->processSocketEvent(ci.sock); + ci.server->processSocketReadEvent(ci.sock); if (ci.sock->isShutdown()) { remSocket(ci.sock); return; |