Communication Between Service and Form Application

This is possible, and as you probably suspect, a common task when working with services. Because they have no interface, services often include an interface for a windowed program to interact with them. 95% of the time, this is done with a built-in socket server. It's easy enough to do with the Indy components ( http://www.nevrona.com/indy ), but you can do it with the built-in socket objects as well. You may find other IPC methods acceptable as well, such as named or anonymous pipes, and mailslots. Sockets are just as easy (or easier), and work from remote machines, and have less overhead the the others. The other methods are not yet ported to .NET. You'd probably have to P-Invoke to use them. When you only need to READ the status of the service, a database can often be the best way. The service can write to the database at its leisure, and the windowed program can read at its leisure.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

spgilmore22y ago
This is possible, and as you probably suspect, a common task when working with services. Because they have no interface, services often include an interface for a windowed program to interact with them. 95% of the time, this is done with a built-in socket server. It's easy enough to do with the Indy components ( http://www.nevrona.com/indy ), but you can do it with the built-in socket objects as well. You may find other IPC methods acceptable as well, such as named or anonymous pipes, and mailslots. Sockets are just as easy (or easier), and work from remote machines, and have less overhead the the others. The other methods are not yet ported to .NET. You'd probably have to P-Invoke to use them. When you only need to READ the status of the service, a database can often be the best way. The service can write to the database at its leisure, and the windowed program can read at its leisure.
0