[FreeNX-kNX] NX performance issue

[Fabian Franz]

> > Anyway as direct method is faster anyway, it can be combined 
> > with nxagent. I tried it and it works.

> This idea intrigues me, because it would potentially allow me to implement
> quad-buffered stereo as I currently do with Direct Mode.  The real
> question,
> though, is how to make it work with the Windows NX client (the "free as in
> beer" client from NoMachine.)  Setting a window property containing the
> Win32 window handle would be easy enough, but NXWin doesn't appear to
> allow
> any outside X server connections, so I'm not sure how VGLclient could talk

I think you are wrong here.

I can see now sign in nxproxy that it connects differently to NXWin than to any other X-Server.

And I could run a remote XTerm with NXWin just fine.

Though you would need three translations here:

internal nxagent -> external nxagent -> Windows winid.

> to it.  Apart from that, though, this seems like the right idea --
> probably
> easier than diagnosing nxproxy performance issues.

Yes, much easier. Same problem occurs using a forwarded cups channel by adding cups=1 and cups=8000 to the proxies.

cu

Fabian