SoapHttpRouter Class
Provides the routing handler for a message path intermediary.
Namespace: Microsoft.Web.Services2.Messaging
Assembly: Microsoft.Web.Services2 (in microsoft.web.services2.dll)
Usage
'Usage
Dim soapHttpRouter1 As New SoapHttpRouter()
Syntax
'Declaration
Public Class SoapHttpRouter
Implements IHttpAsyncHandler, IHttpHandler
public class SoapHttpRouter : IHttpAsyncHandler, IHttpHandler
public ref class SoapHttpRouter : public IHttpAsyncHandler, IHttpHandler
public class SoapHttpRouter implements IHttpAsyncHandler, IHttpHandler
public class SoapHttpRouter implements IHttpAsyncHandler, , IHttpHandler
Remarks
The routing handler takes an incoming message and sends it to the next via, after verifying that it is the top most via; or sents it to the to.
The routing handler also checks the referral cache to determine the next hop for the message based on the next via. If there are changes, it adds the new via element to the path header and sends the message to the new location.
If the handler finds a rev path, it will add it. But this path isn't used by any other feature. Users can get at it and even set it.
The WSE routing handler does not add a path element to a normal response messages, but it will generate a path for a routing failure if one occurs. The relatesTo element is not used in the WSE implementation of routing.
The SoapHttpRouter is an implementation of the System.Web.IHttpHandler interface as found in ASP.NET. Developers cannot override this. Classes that implement the IHttpHandler interface are provided a reference to an HttpContext object for the current HTTP request. The object provides access to the intrinsic Request, Response, and Server objects for the request. A SoapHttpRouter is installed into an application by registering the handler as an HttpHandler with ASP.NET in the Web.config file.
Inheritance Hierarchy
System.Object
Microsoft.Web.Services2.Messaging.SoapHttpRouter
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Platforms
Development Platforms
Windows XP Home Edition, Windows XP Professional, Windows Server 2003, Windows Longhorn, and Windows 2000
Target Platforms
Windows 2000, Windows 2000 Server, Windows 2000 Advanced Server, Windows XP Home Edition, Windows XP Professional, Windows Server 2003, Windows Longhorn, Pocket PC, Windows CE, Smart Phone
See Also
Reference
Microsoft.Web.Services2.Messaging Namespace