Shulou(Shulou.com)06/02 Report--

This article mainly introduces "what the WCF bearer environment is like". In the daily operation, I believe many people have doubts about what the WCF bearer environment is. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts about "what the WCF bearer environment is like!" Next, please follow the editor to study!

CF is still used by a lot of people. Don't know if you are using it now? If you don't use it, you will be out of date. Let's analyze the problem of WCF hosting environment. Microsoft's efforts to ensure that service developers do not think too much about the WCF hosting environment is commendable. ServiceHost removes all technical difficulties, allowing you to focus on the service logic without having to think too much about how to host the service. You must choose a host according to your specific requirements. WCF is mainly written as a programming model, and one of its main design purposes is to achieve "host agnostic". ServiceHost doesn't care where it is instantiated, as long as you want the service to be accessible when it is running. That is, it requires a process running a .NET application domain.

When choosing an application type, you must consider certain requirements (for example, whether the program is a console application or a WinForms application, and so on). ServiceHost must be instantiated to provide the WCF hosting environment needed to run the service. Typical .NET applications (for example, console applications and WinForms applications) typically run on the user's desktop computer. These environments do not always run, they can host your services, but they are not typical hosts for enterprises. We believe that hosts for enterprises should be able to support a larger service-oriented architecture in which multiple systems rely on key business functions exposed by services. These hosts for enterprises can usually meet requirements such as high availability. Therefore, we cannot use the console or WinForms application as a host for the enterprise.

Typically, the service runs on the server and is managed and operated by the operator. Operators managing the server generally do not want to manually start the console application or the WinForms application when the server is restarted. In order to enable service applications to run in the data center, for enterprise service-oriented situations, the feasible solution is to host the service on the IIS or as a Windows service.

Sometimes you need to implement interprocess communication on the user's desktop computer. In this case, the service is active only when the user uses the application. Typical applications that require interprocess communication are console applications and WinForms applications. These applications are suitable for hosting these types of services.

To be able to determine which host is best for your situation, you should consider non-functional requirements. In general, non-functional requirements specify the technical requirements of the application to ensure that it meets the quality and maintainability required by the application. For WCF applications, non-functional requirements actually involve the following:

◆ availability: when do you want to access your service?

◆ reliability: what happens when the service is interrupted for some reason? How will this affect other users of the service?

◆ manageability: do you need to easily understand what is happening on the host hosting the WCF service?

◆ versioning: do you need to provide support for older versions of services? Do you know who is using your service?

◆ deployment: what deployment model should be adopted? Do you want to install through the Microsoft Installer process and the Visual Studio deployment package, or can you use xcopy to meet your needs?

◆ status: is the service stateless? Do you need a conversation?

Based on these non-functional requirements, you can determine which hosts meet your needs. To help you make a choice, the rest of this chapter describes the different WCF hosting environments and their advantages and disadvantages. Note that because you don't know your own operating environment, it's always possible for the WCF programming model to switch to a different host, but that doesn't mean you have to change the service implementation. First, you need to self-host in the console application to test and determine the prototype of the service.

At this point, the study on "what the WCF bearer environment is like" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.