Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MSSoapInit2 vs MSSoapInit

661 views
Skip to first unread message

Bryan

unread,
May 29, 2003, 8:26:08 PM5/29/03
to
Hey,

In terms of performance, what's the difference between the MSSoapInit2 and
the MSSoapInit mothed? Does anyone know to speed up the soap connection?

Thanks.


SQL Server Development Team [MSFT]

unread,
May 30, 2003, 1:15:13 PM5/30/03
to
The code is the same - mssoapinit is there for backward compatibility. The
three ways to speed up mssoapinit init are:
1) Load the WSDL from a local file instead of over the network
2) Make the WSDL smaller - not always possible but it may make sense to
split a WSDL with many methods into multiple WSDL's with fewer methods
3) Don't call it - be sure you're holding on the the initialized Soap Client
if you think you may need it again. Many people open the connection for
each Soap method which is very expensive.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

"Bryan" <bt...@consensusmed.com> wrote in message
news:u8RKLIkJ...@TK2MSFTNGP12.phx.gbl...

Villi Bernaroli

unread,
Jun 3, 2003, 3:05:30 AM6/3/03
to
"SQL Server Development Team [MSFT]" ha scritto

> 1) Load the WSDL from a local file instead of over the network

Hi, what kind of changes do I need to apply to the WSDL, in order
to put it on all clients' C: ?
I think the "SOAP:address location=" section, in the following
part of the WSDL, should be modified:

<service name='ws_test' >
<port name='ws_testSoapPort'
binding='wsdlns:ws_testSoapBinding' >
<soap:address
location='http://SRV-PROD/WS_DEVPATH/ws_test.WSDL' />
</port>
</service>

Or not?

Moreover, for the clients, do I only have to change the path I
specify with MSSoapInit, giving it the path of the local WSDL
instead of the remote one?

TIA,
Villi


Roger Wolter[MSFT]

unread,
Jun 4, 2003, 12:57:30 PM6/4/03
to
No, you don't have to change the WSDL at all. Just change mssoapinit and
replace the URL with a full path to the WSDL file.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Villi Bernaroli" <novil...@tinspam.it> wrote in message
news:uPhHJ6ZK...@TK2MSFTNGP11.phx.gbl...

Villi Bernaroli

unread,
Jun 5, 2003, 9:07:09 AM6/5/03
to
"Roger Wolter[MSFT]" ha scritto

> No, you don't have to change the WSDL at all. Just change
mssoapinit and
> replace the URL with a full path to the WSDL file.

Yeah, I have seen it.

Trying it out, it seems that keeping the WSDL local is useful
only for the call of the MSSoapInit method (gotta download the
wsdl), than the subsequent calls to the methods of the SOAP
object don't get hurried. So said my tests, anybody else has had
different results?

Thanks
Vilco


0 new messages