[WSE] Web Service-background listening Service establishes a subscription/publish relationship through WSE2.0

Because the Web Service Execution identity is restricted, we cannot directly apply for a Web Service as a SoapReceiver, but use the following web. config definition to define the virtual directory. the end point of ashx, And the subscription/publish mechanism between the service and the background listening service is implemented through WS_Addressing and WS_Messaging.
<Configuration>
<ConfigSections>
<Section name = "microsoft. web. services"
Type = "Microsoft. Web. Services. Configuration. WebServicesConfiguration,
Microsoft. Web. Services, Version = 2.0.0.0, Culture = neutral,
PublicKeyToken = 31bf3856ad364e35 "/>
</ConfigSections>
Principles:
In addition to the in-process and TCP communication mechanism, you can also integrate SoapReceivers with the HTTP pipeline in ASP. NET. If you look at the definition of SoapReceiver, you will notice that it implements IhttpHandler:
Public abstract class SoapReceiver: SoapPort, IHttpHandler
{
...
}
Because of this, any SoapReceiver or SendService class can now be configured as an HTTP handler in ASP. NET. By adding a new ing in the httpHandlers section of the web. config file, you can configure the http handler. The web. config item maps the verb/path combination to the SoapReceiver type:
<System. web>