|
albartell wrote: > And if you wanted to take out all of the learning curve of doing raw sockets > (and all the "fun" that comes with it) you could just install a stripped > down version of Tomcat on the PC. That way all you would need to do is write > a regular old servlet that would listen for requests. But writing a RPG app that talks servelet language is probably harder than writing a java app that listens for basic requests. Another option is to use data queues to transfer the requests ... simply create a keyed data queue based on client IP address, have the webfaced app add the request to the data queue, and have the java server application (running on the client PC) simply wait on the data queue. No socket coding required on either side. > Tomcat may be overkill for your situation though so make sure there is a > good enough reason to load it. IMHO, Tomcat is overkill in just about any client application ... although I know it's used by a few client applications. > Speaking of your situation, I have always wondered how technologies like > GoToMyPc.com and MyWebExPc.com work? I know they are running a Java client > that some how broadcasts its IP address to a main server which then allows > me to connect to my home PC from where ever I am. The client registers itself on the server and simply polls for activity. It doesn't broadcast it's IP, because 9 times out of 10 the remote system isn't exposed on the internet. The remote PC is a client that connects to the remote server. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.