system services development

  • Thread starter Thread starter young_leaf
  • Start date Start date
Y

young_leaf

hi

i am making an Interprocess application, between 2 or more computers.
what is the best way to do it.

this is all i need: to Send command to client app,
to Query for status of client app.

i made a win32 application that does something. like read a certain
Binary file and load some of it to memory.

Now, that "loading" should be done only when the "server" app
controlled by a User wants to.
so, can a service be created to call that win32 Application and invoke
functions.

should it be developed using ActiveX or COM?

Thx
 
young_leaf said:
i am making an Interprocess application, between 2 or more computers.
what is the best way to do it.

this is all i need: to Send command to client app,
to Query for status of client app.

i made a win32 application that does something. like read a certain
Binary file and load some of it to memory.

Now, that "loading" should be done only when the "server" app
controlled by a User wants to.
so, can a service be created to call that win32 Application and invoke
functions.

should it be developed using ActiveX or COM?
Click to expand...

Almost every computer these days has networking support. You could use plain
old WinSock.

You can also use pipes, mail slots, RPC, NetDDE, and DCOM.

There is no best way for every purpose. You may want to read up on your
options here:

http://msdn.microsoft.com/library/d...n-us/ipc/base/interprocess_communications.asp

Regards,
Will
 
i don't know if it will be an issue or not, but if you have lots of
different platforms, plain sockets give you the most freedom. you also don't
have to care about registering components etc.

kind regards,
Bruno.
 
Back
Top