All the year round, we use a computer to change. Today, everyone sees the value of the Internet, and we use a computer to become more and more relying on the service provided by the network. As far as I, I like to buy things through the Internet, get traffic information, compare products, buy tickets, and read products.
However, I found that there are many things I want to do today, I can't be implemented. For example, I want to find a restaurant with a detailed introduction in my community. In addition, I want to know if this restaurant is still vacant at 7 o'clock tonight.
Or, if I am doing business, I will want to know the details of the seller. If there are multiple sellers to provide information, I want to know which seller's goods are the cheapest, or which seller can deliver the fastest.
There is no such service today, there are two main reasons. The first reason is that there is no suitable standard to describe all information types. The second reason is that today's merchants tell others what they are selling in their own way. The emergence of XML provides a standard that describes all information types. The second reason can be concatenated as: in order to provide such services, development work must be difficult.
Microsoft's foreseeable service will be the road to the future. In other words, the company will provide the service and the user who is served will pay the service. Many services will be free, and some services will charge or charge by users. When writing this article, how personal and business companies pay for these services are unclear; we must first see how this business will be carried out. You can regard the service as the implementation of some business abstraction. Here is some simple service examples:
Convert postal coding to latitude and latitude position;
Verify the purchasing power of the credit card;
Find ways to reach another place from a certain place;
Find a restaurant needed;
Manage an online image;
Control a online calendar;
I can continue to imagine a company that should be implemented.
Without doubt, Microsoft will provide some such services in the near future. Other companies will provide other services, and they can fully participate in (even with Microsoft) to a free market.
So, how do we reach the future of those services from today? And, how do we use the concept of combining services to make applications that really have a rich feature (this application is based on HTML or other way)? For example, if all restaurants provide a list of services listed in the menu, you can make such an app, which can find a restaurant that users want to eat. By querying the menus of each restaurant, find the cooking flavor or dishes with users, and is in the restaurant near the user.
To make an app, the service provider must be a logical interface on their business service providers. This programming interface must be invoked by the remote to remotely, such as the Internet. This is Microsoft.Net INITIVE.
Let me explain it this: Computer and peripherals (memory, monitors, digital cameras, scanners, and others) are connected. The development platform provided by the operating system (like window) makes the application abstract access to these peripherals. In this way, you can regard these peripherals as a service. In the new world, service (or peripherals) will be connected to the Internet.
Developers want to get a simple way to access these services. Microsoft.Net Initiative offers this development platform.
It can be determined that Microsoft does not have any standards involving events that will actually occur in the future. Communication between applications and services is done through the HTTP packet on the Internet. Inside the HTTP package is the XML data that needs to be served, then the server completes the response by sending XML data back to the customer. XML data has formal standards. This standard is called a Simple Object Access Protocol (SOAP). Microsoft helps define these standards, but do not own these standards. The following graph shows a web service group that communicates with each other to send XML data through the SOAP protocol. The graph also shows that the customer can communicate via the SOAP (XML) mode via the web server and other customers. In addition, the graph shows the service results of the HTML form from the client from the web server. Of course, it may be necessary to fill in a web table that gives a web server. The web server handles the customer's request (including communication with other web servers), and the result will be finally returned to the customer through the standard HTML page.
In addition, the operating system that can be accepted for these SOAP requirements must be run on a computer that provides services. This operating system may be a window operating system, but it is not necessary. Any operating system that can receive requests on the Socket port and can read the port on the port. In the near future, cellular phones, mobile, automotive, microwave, refrigerator, watch, stereo, game console, and various other devices will be able to participate in this new world.
In the customer or app, the operating system must be able to read / write to the socket port, so that the service requirements can be issued. In addition, the operating system running on the client computer must support any requirements for the end user application. If the end user's application wants to make a window or menu, the operating system must provide this feature, or the developer of this application must be implemented manually.
Of course, Microsoft wants people to use the extensive characteristics of the window to prepare applications. However, this is not necessarily necessary. I am trying to say whether I will happen whether it is Microsoft's participation. Microsoft's technology does not cause these changes. Microsot.net is made to make developers to make these services and access these services. Today, if we need, we can make our own operating system. But it is really difficult and will take a long time. We can write web services and write procedures for receiving and handling SOAP requirements. But it is also difficult.
Microsoft has completed all difficulties for us in order to produce Microsoft.Net. It makes these work simple. Now, like our application developers, you can concentrate our energy on our own business abstraction concept and service. As for communication protocols and builds, they are handed over to Microsoft. (This may be the real reason for Microsoft has many developers who like it).
The hoses are letter:
I haven't contracted it for a long time, is everything going well?
I saw a comment on the Jeffrey Richter on the .NET on CodeGuru. I really like the "Programming Application for Microsoft Windows", so I simply translated it.
Now discussing that .NET is very much, I hope this short introduction can throw bricks, let more people seeks to express their views.
