Nevermind I figured out a solution to the problem. If anybody's
interested, the way I solved the problem was allowing my server to
call "sock.Listen", and then when the other application was launched,
I called "socket.Connect" in the client, passing it the IP address and
Port of the server. This way I can develop communication between two
C# applications where the server launches the client.
Thanks for reading!
~ Maryam
On Mar 15, 8:08 pm, ahmed.mar...@gmail.com wrote:
> Hi all,
>
> I have a weird situation here in that I've designed two C#
> applications that need to communicate with each other using sockets.
> So I am trying to set the applications up in a way that one acts like
> the 'server' and the other a 'client'. However, the 'server' is an
> application that does some work, and one if its jobs is to launch the
> other application and start communicating with it when a user clicks a
> certain button. The other application will then open up and begin
> passing data back and forth with the 'server'. The problem is, how do
> I get the SERVER to INITIATE communication with a CLIENT instead of
> waiting for a connection the way servers traditionally do?
>
> Any ideas how I could approach this problem? Thanks!
>
> ~ M
|