Netbeans + RDP + x*1000km = indescribable brakes of the editor?

Question

NetBeans

I'm finally going on vacation, %username%. But anything can happen - and there should always be terminal access to the development environment. And not nominal, but quite efficient.
My development environment is netbeans 7.0 , running on Windows 7 64bit. Accordingly, I use the usual RDP . There is also Visual Studio and SSMS. So with the last two - no problems, there is a slightly noticeable input delay (ping is about 90 ms).
But netbeans, when scrolling at least one line, redraws the entire window for about 2 seconds, while consuming almost 600 kb of traffic. I installed VNC - it's even worse with it. Radmin and others have not tried - we have 100% licensed software, but somehow I don’t feel like buying it myself ... I will gladly consider free solutions.
Have you, %username%, encountered such a problem? And does it have sane solutions (shouts put netbeans on Linux - they don’t roll, I don’t have an extra server).

Answer 1

TeamViewer is still there, you can try it. Very comfortably.

Answer 2

Netbins work in Java, and Java has its own gui... So you're out of luck, RDP redraws every pixel of your netbins :-)

Answer 3

I honestly can not understand why turn technology around?
Put the environment locally and DVCS + VPN. Moreover, netbeans is one of the least resource-demanding and fairly mobile IDEs.

Answer 4

Miracles don't happen. Of the free ones, nothing will definitely help you. Unless the citrix protocol may turn out to be more optimized, but it costs a lot of money.

Answer 5

I can offer a very curved, but perhaps more productive way. Put a virtual machine on the machine, go to the virtual machine via RDP or another remote protocol, and from there go to your computer via RDP. In this case, the window will be redrawn locally, and just a picture from the virtual machine will be transmitted to X1000 km.
That is, you get, as it were, a proxy for preliminary rendering. Perhaps it will be faster.

Answer 6

Due to the redrawing algorithm, this should slow down.
Alternatively, try Citrix or NX.