>> 500:remote.server.net >> >> where "500" is the port number and "remote.server.net" is the IP >> address of the remote server. In this case there should be a server >> process listening the port 500 in the remote system, which would >> receive the requests from plugins and provide the service. But if you >> wish to run a local service, you would just use >> >> 500:localhost > > Right, if one can configure Ghemical to listen to a port like that... > brilliant!
I know nothing about Ghemical ... If it has a server that already listens to a port then we should use that. >> I have to admit that I have not worked with sockets before, but it >> doesn't sound too hard. :) All servers (httpd telnet etc) work using >> the same priciple I think. > > Yes, it works just like that... In the past I played with sockets... > it's really very nice they way it is done in Java... If Ghemical does not have a server then I recommend that you access it through a .cgi on a web server. I believe the web server approach has a number of advantages. If you start writing your own server then you may get bogged down with a number of issues that are unrelated to the problem you are trying to solve. I don't have much time right now ... but we can talk later. Miguel ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
