How do VNC clients know when to request screen updates?
I am developing a VNC-compatible server, following the RFC 6143 specs, and using UltraVNC as client.
I noticed that, although sometimes everything works pretty well, most of the times UltraVNC does not send FramebufferUpdateRequest messages. As an result, my server does not send FramebufferUpdate and the screen is stuck. Clicking the "Refresh" button, at UltraVNC's toolbar, produces a screen update normally.
I've done some tests and I discovered that, when this issue happens, UltraVNC does not send anything to my server, and the TCP traffic remains empty (the socket is not closed), unless there is some user input (mouse/keyboard) or the user clicks the "Refresh" button.
I thought about sending FramebufferUpdate regardless of the client having requested it or not, once I detected screen changes (or after user inputs). This worked well and I had a real-time screen broadcast, however it looks like UltraVNC could not handle user inputs (keyboard and mouse) anymore since the traffic was clogged up with FramebufferUpdates. Also, this seems to go against the specs, since it says that FramebufferUpdates can only be sent in response to one or more FramebufferUpdateRequests (in VNC, servers only send framebuffers when requested by clients).
So, my questions are: how do I tell the VNC client that some region of the screen was updated, "suggesting" it to send a FramebufferUpdateRequest, if this is possible? Also, what does UltraVNC takes into consideration in order to emit a FramebufferUpdateRequest? It does not look like it is interval-based, nor based in user inputs...
vnc
add a comment |
I am developing a VNC-compatible server, following the RFC 6143 specs, and using UltraVNC as client.
I noticed that, although sometimes everything works pretty well, most of the times UltraVNC does not send FramebufferUpdateRequest messages. As an result, my server does not send FramebufferUpdate and the screen is stuck. Clicking the "Refresh" button, at UltraVNC's toolbar, produces a screen update normally.
I've done some tests and I discovered that, when this issue happens, UltraVNC does not send anything to my server, and the TCP traffic remains empty (the socket is not closed), unless there is some user input (mouse/keyboard) or the user clicks the "Refresh" button.
I thought about sending FramebufferUpdate regardless of the client having requested it or not, once I detected screen changes (or after user inputs). This worked well and I had a real-time screen broadcast, however it looks like UltraVNC could not handle user inputs (keyboard and mouse) anymore since the traffic was clogged up with FramebufferUpdates. Also, this seems to go against the specs, since it says that FramebufferUpdates can only be sent in response to one or more FramebufferUpdateRequests (in VNC, servers only send framebuffers when requested by clients).
So, my questions are: how do I tell the VNC client that some region of the screen was updated, "suggesting" it to send a FramebufferUpdateRequest, if this is possible? Also, what does UltraVNC takes into consideration in order to emit a FramebufferUpdateRequest? It does not look like it is interval-based, nor based in user inputs...
vnc
add a comment |
I am developing a VNC-compatible server, following the RFC 6143 specs, and using UltraVNC as client.
I noticed that, although sometimes everything works pretty well, most of the times UltraVNC does not send FramebufferUpdateRequest messages. As an result, my server does not send FramebufferUpdate and the screen is stuck. Clicking the "Refresh" button, at UltraVNC's toolbar, produces a screen update normally.
I've done some tests and I discovered that, when this issue happens, UltraVNC does not send anything to my server, and the TCP traffic remains empty (the socket is not closed), unless there is some user input (mouse/keyboard) or the user clicks the "Refresh" button.
I thought about sending FramebufferUpdate regardless of the client having requested it or not, once I detected screen changes (or after user inputs). This worked well and I had a real-time screen broadcast, however it looks like UltraVNC could not handle user inputs (keyboard and mouse) anymore since the traffic was clogged up with FramebufferUpdates. Also, this seems to go against the specs, since it says that FramebufferUpdates can only be sent in response to one or more FramebufferUpdateRequests (in VNC, servers only send framebuffers when requested by clients).
So, my questions are: how do I tell the VNC client that some region of the screen was updated, "suggesting" it to send a FramebufferUpdateRequest, if this is possible? Also, what does UltraVNC takes into consideration in order to emit a FramebufferUpdateRequest? It does not look like it is interval-based, nor based in user inputs...
vnc
I am developing a VNC-compatible server, following the RFC 6143 specs, and using UltraVNC as client.
I noticed that, although sometimes everything works pretty well, most of the times UltraVNC does not send FramebufferUpdateRequest messages. As an result, my server does not send FramebufferUpdate and the screen is stuck. Clicking the "Refresh" button, at UltraVNC's toolbar, produces a screen update normally.
I've done some tests and I discovered that, when this issue happens, UltraVNC does not send anything to my server, and the TCP traffic remains empty (the socket is not closed), unless there is some user input (mouse/keyboard) or the user clicks the "Refresh" button.
I thought about sending FramebufferUpdate regardless of the client having requested it or not, once I detected screen changes (or after user inputs). This worked well and I had a real-time screen broadcast, however it looks like UltraVNC could not handle user inputs (keyboard and mouse) anymore since the traffic was clogged up with FramebufferUpdates. Also, this seems to go against the specs, since it says that FramebufferUpdates can only be sent in response to one or more FramebufferUpdateRequests (in VNC, servers only send framebuffers when requested by clients).
So, my questions are: how do I tell the VNC client that some region of the screen was updated, "suggesting" it to send a FramebufferUpdateRequest, if this is possible? Also, what does UltraVNC takes into consideration in order to emit a FramebufferUpdateRequest? It does not look like it is interval-based, nor based in user inputs...
vnc
vnc
asked Nov 14 '18 at 23:14
Jefrey Sobreira SantosJefrey Sobreira Santos
399214
399214
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310165%2fhow-do-vnc-clients-know-when-to-request-screen-updates%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310165%2fhow-do-vnc-clients-know-when-to-request-screen-updates%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown