DCOM Explained
The "big picture" of DCOM architecture for system designers and technical managers.
TABLE OF CONTENTS DCOM Explained
Chapter 12: DCOM and the Internet
Overview
We have looked at the platform support for DCOM; the next big question most people are likely to ask is does it work over the Internet? This chapter thus looks at Microsoft's approach for supporting the Internet, the products it has, the strategy it recommends its users take, and the links with DCOM.
We will be starting this chapter with a description of the approach taken by some of the other middleware vendors so that you can contrast the approach Microsoft has taken with that used by them. Microsoft's approach is quite different, and we will be looking at the reasons why and the implications of this in this chapter.
How Do Other Middleware Vendors Provide Internet Support?
Several middleware vendors currently support the Internet NCR with TOP END using a module called Java Remote Client services, Transarc with Encina using DE-Light Web Client, and BEA with Tuxedo using a module called Jolt. All of them use an identical approach an approach which uses Java, Web browsers, and Web servers and all of the above products are aimed at organizations wanting to support commercial transactions on the Internet using the Web.
The Internet and its protocols are normally unable to recognize the state of a transaction, which makes the multistep, often complex interactions which take place within a transaction largely impossible to support. DE-Light Web Client, JRC, and Jolt solve this problem by combining distributed transaction processing with software that can sustain transaction...
Copyright Butterworth-Heinemann 1998 under license agreement with Books24x7
