Hi Allesandro, Hope, you may give me an additional hint here. Nowadays small businesses are starting to use servers with connected clients instead of using separate desktops. Right now, all examples j or j3d seem to run on a single system. I checked the docs and found several ways to support client-server applications as RMI (what you suggested) and Sockets. Still I have the idea that these may not be the right approach. For example, sockets are described as a communication link between two programs on the network. I am a little afraid that message passing or protocol checking for every mouse-click, mouse move, and other highly interactive activities may slow down the program severely. Couldn't be even simpler than we expect? I cannot check it here, but what would happen if I simply load the program on the server and try to reach it on the client?
Thanks, Dirk -----Original Message----- From: Discussion list for Java 3D API [mailto:[EMAIL PROTECTED] On Behalf Of Alessandro Borges Sent: Friday, April 23, 2004 9:48 PM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Client Server J3D Just a tip: Use RMI. Your client will connect to your server and send command (actions) as it is in the server itself. Alessandro .......................... ............. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
