That program does sound really nice - what issues did you run into that made you less than happy with it?ASX wrote:apparently it works, and should allow to share the window, (virtualbox in this case) ... similarly to tmux you can disconnect and reconnect later ...however I'm not satisfied ... may be be me ... but I have much better recollection of NX ...
shared testing
Re: shared testing
Re: shared testing
- configuration ... nothing says it need dbus running on the server side, to make xpra-server workskraileth wrote:That program does sound really nice - what issues did you run into that made you less than happy with it?
- no client GUI ... well there is one, but it is so ... raw/rogue ...
- performance while running on low bandwidth (64 KBit/s) .... really not usable ... frequent disconnections
- autotuning (bandwidth/quality <---> algorithm/compression/colors) ... doesn't seems to do its job properly
- if you start two instance of xpra client, you get two applet in systray .. difficult to say which one you want to look at
to recap, very unprofessional looking. ... again .. may be it is me.
Edit:
Xpra can use several connection protocol (ssh,ssl,tcp): The man page suggest that TCP alone is unsecure, yet their client GUI default to TCP. No, it is not me.
- NevilleGoddard
- Developer
- Posts: 517
- Joined: Thu Dec 22, 2016 10:30 pm
- Location: Japan
Re: shared testing
Great idea ASX.
Re: shared testing
I have tried again xpra, this time using high speed connectivity: things works better, of course, still there are moment when the interface is unresponsive.
This behavior is due to "auto" features enabled by default:
- encoding
- speed
- quality
setting these so some values improve greatly the responsiveness
also, turning off the shared clipboard and speakers does help.
This behavior is due to "auto" features enabled by default:
- encoding
- speed
- quality
setting these so some values improve greatly the responsiveness
also, turning off the shared clipboard and speakers does help.