WebServicesClientProtocol Performance

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Erik J. - 18 Feb 2005 00:11 GMT

I noticed that when calling a sample "Hello World" service -- no WS-Security
bits involved -- that the WSE client proxy takes about 2.5 times longer than
the standard "web reference" proxy. Is there something about the underlying
[WSE].WebServicesClientProtocol class that is different than the
[System.Web].SoapHttpClientProtocol (at least for this scenario)?

Thanks,

- Erik

Reply to this Message

SA - 18 Feb 2005 00:22 GMT

Erik:

Yes, there are multiple filters, both at the client and the server, that are
called when you enable the project for WSE 2.0.

If you don't need WSE 2.0 features, don't use the proxy with the "2" at the
end. Your performance then should be roughly the same. At the server, you
will still need to pass through those filters though. (Unless you're calling
a web service that doesn't have WSE 2.0 enabled, in other words, where there
is no soapExtensions entry for WSE 2.0)

Signature

Sven.

> I noticed that when calling a sample "Hello World" service -- no WS-Security
> bits involved -- that the WSE client proxy takes about 2.5 times longer than
[quoted text clipped - 5 lines]
>
> - Erik

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...