This is pretty complicated and is fixed with X-windows. What happens,
is the client (GUI) creates an X-Window and attaches callbacks to the
window and then passes that X-Window id to the server. The server
then attaches to the window and adds its own set of callbacks to the
window. X-Windows then does all the negotiation between the two. The
client and server then communicate over the socket to let each other
know what's going on, but some of the interaction is actually done
within the X-server itself.
Much of this is not possible within the Windows frameworks (this is
what makes it so complicated to port--let alone the specialized
custom widgets).
David
I would like to understand the OpenDX architecture
better. I understand that it is client-server. I
understand that the client generates the network
file that is then sent to the server over port 1900.
But what happens when the server is asked to render
something, e.g., through Image? Does it send the image
back through port 1900 to the client, and then the
client puts it up? Or does is put up an X window on
the client and render into that window? Or something
else?
Thanks....John Cary
--
John R. Cary
Professor, Dept. of Physics, University of Colorado, Boulder, CO 80309-0390
[EMAIL PROTECTED]
ph. (303) 492-1489 fax (303) 492-0642 cell (720) 839-5997
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)257-8530
