TCP/IP for Inter Process Commn

[Guest_imported]

hi,
Do you recommend TCP/ip for inter process communication? My friends used it in their Win2K project.They have some 4 or 5 applications running in the same win2k box communicating to each other via TCP. But the problem is that once in a while(usually 4 to 6 days) the connections are reset automatically.(all the apps get affected). We r trying hard to debug this issue, right now we dont have any idea abt what is causing this.
Any help is greatly appreciated.
Thank You,
Anish

 

[markharr]

For inter-process communication for processes that will always run on the same machine, this is not the most efficient mechanism. However, there is nothing wrong that. It does allow the processes to be distributed among machines fairly easily if it is required at some future time.

Obviously, I don't know the exact details of this application so I can only offer general guidelines. In my view though, more thought needs to be given to error recovery. Create an exception handler that is automatically called when a send fails. The listener also needs to be able to provide recovery.

For C/C++ programmers, a try and catch block needs to be implemented around the send. VB has a similar mechanism.

 

[markharr]

Slight clarification to my last entry. Try and catch are not used for this purpose. They are to be used where it's possible that an application might cause a trap.

The programmer just needs to check for return codes and write error handling code as appropriate.

Sorry for the confusion. I was thinking about another problem I was working on at the time and confused the two in my head.