Matti Paksula
Matti Paksula
@neerdoc didn’t do any IO benchmarks. Just compared startup times (ran uptime from alpine image) - from around 6s on GCP, virtualbox to 1.7s with baremetal kabylake 3.8ghz..
Yet another workaround (based on the @apparentlymart 's "first" workaround) that allows you to have workspace variables in different files (easier to diff). When you add new workspaces you only...
No, the opposite. Every time my normal socket client fails to send "RFB ..." in 100ms, it is detected as a wesocket client > On 5. Aug 2020, at 22.27,...
I have a proxy which detects x11vnc server sent `RFB 003.008\n` and I add `sleep(1)` before the client sends its reply of `RFB 003.008\n` back, then x11vnc (libvncserver) thinks that...
can you give your email and I'll share a screencast? that would be easiest for me
I don't understand how a logfile that says webSocketsHandshake failed from x11vnc helps here? > On 7. Aug 2020, at 15.43, Christian Beier wrote: > > > A log...
Add sleep(1) between client connects server accepts server sends RFB 3......\n sleep(1) client replies with RFB 3.....\n because of the line of code I sent in the first post where...
Yes on client (or more specifically in the proxy) and to recap: the sleep is just repro this "slow client" problem > On 9. Aug 2020, at 9.51, Christian Beier...
this still happens
like isn't this a very straight forward bug? the handshake expects something to come in within 100ms or it changes protocol - on a slow network this always causes protocol...