Chapter 5 of my book is about network access to serviced components. This chapter is splitted into three parts: DCOM, .NET Remoting, ASP.NET Web Services.
- DCOM is still a very useful protocol to access serviced components. This protocol is fast, contexts flow across the wire...
- Checking the SOAP services checkbox with serviced components makes use of .NET Remoting. Using .NET Remoting to access serviced components has some disadvantages, e.g. contexts don't flow. The advantage of this protocol (compared to DCOM) is that clients can be installed with no-touch deployment.
- The third option is using a facade: ASP.NET Web Services. Clients can use Web Services to access the serviced components. In the backend ASP.NET again uses DCOM to access the serviced components.
In this book I will also show Indigo, and how this relates to serviced components. This is in another chapter.