I'm interested in using the code from this project, as the basis for developing a mechanism for transparently running Swing applications remotely. The idea is that while the execution of the application would be tied a machine, its display need not be. Existing remoting technologies require administrative privileges that make them painful or impossible for ordinary (non-administrative) use. Many of them are also geared toward remoting desktops, while remoting individual applications is often more useful.
Would anyone familiar with the SwingAWT codebase like to make some comments about the sanity of using SwingAWT for this? Any pointers to additional documentation or good starting points would be greatly appreciated.
Here are some other projects that may clarify the sort of thing I have in mind.
Hi,
I'm interested in using the code from this project, as the basis for developing a mechanism for transparently running Swing applications remotely. The idea is that while the execution of the application would be tied a machine, its display need not be. Existing remoting technologies require administrative privileges that make them painful or impossible for ordinary (non-administrative) use. Many of them are also geared toward remoting desktops, while remoting individual applications is often more useful.
Would anyone familiar with the SwingAWT codebase like to make some comments about the sanity of using SwingAWT for this? Any pointers to additional documentation or good starting points would be greatly appreciated.
Here are some other projects that may clarify the sort of thing I have in mind.
MetaVNC is a window aware VNC.
http://metavnc.sourceforge.net/
THINC is a remote protocol designed to achieve acceptable performance even in the face of latency.
http://www.ncl.cs.columbia.edu/research/thinc/
http://www.ncl.cs.columbia.edu/publications/cucs-027-04.pdf
Thanks,
Curt