Remembering the Future

We currently give you three "full-featured" ways to send a message from one process to another: MSMQ, DCOM, HTTP. I don't discuss .NET Remoting's binary/tcp protocol, as for one, it's not secure, and secondly, DCOM is typically faster. All three mechanisms allow you to send a secured and structured message from one program to another, including programs running on other machines.

All three mechanisms have rich programmatic support and again, what's interesting is how they differ.

Services and Processes

We currently give you three ways to get a process up and running: NT SCM, COM(+) SCM, and the IIS6 WAS.

All three mechanisms allow you to configure a deployed piece of code to start as a particular user account or one of the three service accounts (NetworkService/LocalService/LocalSystem).

All three mechanisms have programmable access to management and configuration. What's interesting is how they differ.