Date: Thu, 05 Nov 2020 07:50:27 +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-m6U4xTSIVi@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 --- Comment #5 from marko@apache.org --- Thanks for the review, and comments. I'll switch over to head of trunk to do follow-up dev on this code. My bad = for not checking the patch against it. I agree, TX of screen updates needs a bit of followup work. We should honor= the order of client request vs. first TX of server screen data, which hopefully should address that first refresh. I'll look into that. I tested the code with TigerVNC also, rudimentary tests showed it behaving = ok. Admittedly, didn't test it very thoroughly. Interesting observation regardi= ng combination of all black screen block & CRC. It seemed to me that the CRC variation here would produce non-zero results for all black data, but I hav= en't validated that. --=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-m6U4xTSIVi>