Recently I have been asking myself – Why are some people still using Dcom?
I have been using Dcom for quite some time and I have decided to move into something different…terminal services.
I think the main reason for using client-server models is to enable applications to be accessible over a network and to also make sure that we eliminate support costs by making clients as thin as possible. Dcom and terminal services can both achieve this. The question is: Which one is the best in as far as functionality and usability are concerned?
Dcom clients are not thin enough because part of installation is required at the client. This posse a lot of threats for a programmer:
1.The programmer is likely to support the client machine even if it has nothing to do with the application that was installed. I have heard customers saying “your program has ruined my word application”
2.When customers want to change the program interface, the programmer has to update all the client machines.
With terminal services, you just install the program at the server machine and every client machine will use the program as if the user is at the server machine. In this way, the program is truly at the server machine and the client is truly thin (if not non existent because you don’t install any part of the program there). With terminal services, there are no mappings, and the users will refer to their system administrator for most network problems.
If arenot familiar with terminal services please follow this link:
http://www.microsoft.com/windows2000/technologies/terminal/default.asp
So, why are some programmers still using Dcom?
I’m desperate for an answer.