I'm building a Windows service and I need to make a monitoring application
for users. Therefore I'll need to implement some form of communication
between the program on the users' workstations and the service on its own
machine. I'm afraid I'm completely out of my element here.
One of the things I want to do is to make all communication handling in the
service asynchronous, that is, I don't want "client chatter" to interfere
with the core work that the service does. I was looking into the Socket
class, and it appears that it's one of those things where you have to do
EVERYTHING yourself. I mean, it doesn't even seem to raise an event when a
client attempts to connect! Do you actually have to poll the monster
regularly to see if there are pending connections?
Does anyone know of a class (or articles dealing with one) that allows
asynchronous processing (which disqualifies the TcpClient/Listener classes)
and which will also let me write event-driven code?