--- In [email protected], "mr_gees100_peas" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], Thomas Hruska <thruska@> wrote: > > > > mr_gees100_peas wrote: > > > Hi, > > > > > > This is just hypothetical but I guess I have not > > > been able to ask the right question or don't know > > > the proper terminology here. Lets say you have a > > > program running on your pc. You click a button and > > > this program sends a message to another computer > > > (windows pc). A program in that remote pc then recieves > > > the message and does some action. Once the action is > > > done it returns a reply saying that the action was > > > succesfull or not. > > > > > > My question is what do I need to accomplish something > > > like this. LEts say from my pc send a message to a > > > second pc and open the cd drive. Then return a message > > > to tell whether that cd drive did open. > > > > > > That is the best i can describe it. I don't know what > > > would this fall under. I have no code since I don't > > > even know what to google for to begging with. > > > > Interprocess Communications (IPC). TCP/IP sockets, > > named pipes. > > Remote Procedure Call (RPC). Pretty old-school stuff. > > This is the heavy-weight version of IPC. Generally > > superseded by things like CORBA.
I dare to disagree. RPCs are still in heavy use, and because they don't force you to deal with authentication mechanisms and security issues on a higher level they usually cause far less overhead and hassle than CORBA, web services, and the like. > > CORBA. Have no idea what it means nor have ever had a > > need to use it. Generally superseded by SOAP/WSDL/ > >Web Services. <snip> CORBA is the abbreviation for Common Object Request Broker Architecture. This architecture is meant to allow arbitrary applications to push "objects" (in the OOP sense of the word, meaning data and methods are encapsulated in one entity) to some recipient, have the requested methods be executed, and retrieve the results back. Web services and the like (here I completely agree with Thomas) are a complete overkill for such tasks. They usually come in handy when it comes to publishing applications over the internet, but despite that I would use them with extreme caution. TCP/IP, though just the technical basis for all those (and many more) things, is extremely easy to use; the two things one has to care about are: - authentication, - re-establishing broken connections. Just my 2 pennies. Regards, Nico
