Date: Fri, 06 Nov 2020 14:06:48 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 250795] support RFB 3.3 for VNC client interoperability Message-ID: <bug-250795-27103-1zVs7Vlm6U@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250795-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-250795-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250795 marko@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #219296|0 |1 is obsolete| | CC| |marko@apache.org --- Comment #6 from marko@apache.org --- Created attachment 219393 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D219393&action= =3Dedit svn diff output of the relevant changes; ver2 Here's an updated version of the patch, which includes additional performan= ce fixes. I incorporated Henrik's changes from the pointed diff; the most important performance improvement from there was the fact that the server would not s= end an update until client requests one. I also reduced the amount of memory allocated for CRC buffers. It was compu= ted slightly incorrectly, but ended up allocating 32 times too much memory. Behaviour changes are now that a) support RFB protocol versions 3.3 and 3.7= for authentication, b) don't send first screen until client asks for it c) don't send updates (at all) unless client has asked for it AND we have data to se= nd. I've tested this against tightVNC, realVNC, apple's screen sharing, tigerVN= C, krdc and vinagre. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250795-27103-1zVs7Vlm6U>