Routing Web-Service Traffic

The Silk Performer .NET Framework can route Web traffic generated by .NET components through the Silk Performer Web engine. This means that the Web engine executes the actual Web requests, enabling you to see exactly what is sent over the wire. You can also use features of the Silk Performer Web engine, like modem simulation, IP multiplexing, network statistics, TrueLog, and others.

By default all network traffic is routed through the Web engine. You can switch the routing off and only enable it for specific Web-service client-proxy classes. To switch the routing on for specific Web-service client-proxy classes, you need to change the base class of the proxy classes from SoapHttpClientProtocol to SilkPerformer.SPSoapHttpClientProtocol. Changing the base class allows the Silk Performer .NET Framework to generate more detailed statistical information for each Web-service call. We recommend that you enable this feature for all your Web-service proxy classes. You can enable this feature by using the Web Service dialog box in Microsoft Visual Studio, which is accessible through the Silk Performer menu.

For each Web-service call a node is created in the TrueLog with the SOAP envelope that was passed to the Web service and returned to the client.

If detailed statistical information for Web-service calls is disabled, the .NET HTTP classes process all requests.