Microsoft's. NET Policy (2)

Policy. NET describes two programming models

On the technical level,. NET platform is based on the extension of the subscript language, which is our familiar XML, simple Object Manipulation protocol (plain Access Protocol, SOAP), and the idea of future Internet as a service for a variety of devices. These high-level descriptions are primarily geared toward the most obvious aspect of the new model-the part that implements Web services.

However, in the interior,. NET platform is built on the. NET architecture, the. NET architecture provides the underlying mechanism of the APIs that implement these concepts. NET architecture also goes through the problem of. NET itself-that it is used to describe too many things. In particular,. NET describes two new and different programming models that form the basis of the concept: the Web Services Programming model (Web service programming models), and the System programming model (Systems programming models).

Enterprises must recognize that composition. NET is two independent programming models. The Web Services programming model and the underlying system programming model are independent of each other. These programming models can and should be used separately.

. NET Web Services Programming model
. The Netweb service programming model is largely the implementation of various interfaces through the Internet's various standards. This is a set of loose models based on Internet standards, using HTTP and other protocols as the primary communication mechanism, while using the Xml,soap,web Service Description Language (WEB services Description language,wsdl), and general description, Discovery, Integration (Universal Description, Discovery, and Integration, UDDI). Initially, the use of most of these programming models will take a request/answer pattern.

In 2003, the main form of Web services would be component calls and information push, which accounted for more than 75% of all Web services. A more long-term future, we think that the "coordinated organization" of workflows or services will be the backbone of Web services, and many of these programming models have emerged, such as soap and other technologies that appear in. NET, and these technologies are now available, before a formal. NET product.

As an increasing number of Web service systems,. NET architecture provides a programming model that is independent of the underlying system APIs and component models. This also reflects the views of Microsoft and others on distributed computing in the 90 's, and has been implemented in a simple way via the Internet. Services are implemented in the form of programs on the server that use standard protocols to talk to the invoked program.

If you need to communicate across components in one process in a system, or across. NET architecture system or multiple processes for cross component communication. NET schemas can communicate using SOAP or binary protocols. If you are in a cross system environment (for example, and non-. NET architecture System) for component communication. NET schema can only use soap. Programs and services running on one system still use COM, but will later become used. The new class in net.

In theory, these programs can also be enterprise JavaBeans implemented on UNIX, but Microsoft has not provided any help for this. But remember that the. NET Web Services programming model is not dependent on the. NET system programming model.

. NET System Programming Model
As. NET platform, Microsoft has also created a new system programming model, as well. NET architecture. The. NET system programming model will eventually replace the COM and Windows APIs in the long run, and this model, which is not yet named, uses a new base class.

The. NET Framework (. NET Framework) contains the Microsft new common language runtime (Common Language Runtime, CLR) that supports the new programming model and, for the first time, the real object-oriented class structure as part of the run-time environment. The functionality provided by the COM interface for developers is also available in the. NET architecture.

The. NET system programming model is Microsoft private, although some parts are open, due to the efforts of the European Federation of Computer Manufacturers (European Computer Manufacturers Association, ECMA) in C # standardization. NET system programming model also includes classes and mechanisms that can transform existing programs into Web services, which simplifies the development of Web services, although such settings are not very necessary.

Microsoft's Chairman, Bill Gates, is going to do this. NET platform migration is as significant as from DOS to Windows. But we think a more accurate comparison should be that this migration is similar to the migration of Win16 to Win32. In the migration to Windows, DOS programs immediately become the past, while Win16 applications are largely compatible with Win32.

Another good comparison is putting. NET compared to when Mirosoft implemented its own Java, when Microsoft packaged Java classes and components as COM components, Microsoft learned the benefits of mapping the two models to each other. Now that Microsoft is starting to develop a new component model that does not have a name, they map and package the old and new models again, and the old model is one of the real intentions of com,microsoft here is to remove the need for Java.