Newsgroups : Borland : borland.public.delphi.nativeapi.win32 : 2005 Feb : WinSock and Interprocess Comms.
| Subject: | WinSock and Interprocess Comms. |
| Posted by: | "RandomAccess" (randomacce..@monaco.mc) |
| Date: | Mon, 21 Feb 2005 01:01:08 |
I've downloaded the excellent ICS internet components annd I am now trying
to develop a strategy for some interprocess communications.
I have never used Winsock before but it looks straight forward.
I'd like to know if the following is ok or whether there are any problems
with this approach.
Several copies of my app will be running on various machines on a LAN. One
of them will be configured as a server in order to maintain synchronization
of data between the other running copies of my app.
I imagine that when each copy starts up, it would contact the server and
establish a WinSock connection to it through a Port setup soley for this
purpose. The server then creates a Winsock connection using another port
solely for comms with that remote system.
When *any* remote copy of my app updates data, a message needs to be sent
to the server, so that the server can update itself and send messages to
the *other* instances of my app running on other remote machines.
Questions :
Can my server app have multiple WinSock servers running simultaneously as
I've suggested?
Is multithreading required in order to do this?
Any ideas, help would be appreciated
best regards