|
-
May 18th, 1999, 10:02 AM
#1
Communication betweens apps on two different NT machines
Hi all,
looking for a bit of advice here.
I have an application (might end up being a service) that will run on an NT machine waiting for information from an app on another NT machine.
Basically, PC1 is doing a load of work and when it is finished it will send a message to PC2, when PC2 gets the message it will pop up some window to tell the user that the work has finished on PC1.
I am looking for advice on what type of communication to use (can be used)
I initially thought TCP/IP 'cause I have some experience with this, but jut wondering if there is another (and/or better) way.
-
May 18th, 1999, 10:47 AM
#2
Re: Communication betweens apps on two different NT machines
Yep, the socket will be the best way to do it
-
June 28th, 1999, 07:00 AM
#3
Re: Communication betweens apps on two different NT machines
see NetMessageBufferSend. Is easy to use.
-
June 28th, 1999, 07:13 AM
#4
Re: Communication betweens apps on two different NT machines
Personally I'd put a COM object on PC2 and let DCOM handle the low-level stuff.
-
June 28th, 1999, 07:36 AM
#5
Re: Communication betweens apps on two different NT machines
You could also consider using IDL.
Martin van den Berg
High Tech Automation
The Netherlands
[email protected]
-
June 28th, 1999, 10:02 AM
#6
Re: Communication betweens apps on two different NT machines
You could also use named pipes.
-
June 29th, 1999, 04:09 AM
#7
Re: Communication betweens apps on two different NT machines
if you want to write it as service use ATL to create the framework for you and DCOM for communication, you will have much flexibility...
chrislaw
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|