Hi everyone,
We have run into above problem recently. All I found so far are other
people complaining that 1st invocation of a Web Service can be very
slow, the problem size (delay) seems to depend on number of methods
(maybe even exponentially) and no one knows of a solution (other then
writing the client proxy yourself). Note I am talking about the client
side (similar problem occurs on server side but is less severe since
the server should in principle be up all the time, so paying the
penalty once it tolerable). Some references I saw are below.
As I understand the problem is has to do with dynamic code creation
and compilation on the client during construction of the proxy, in
order to enable Soap serialization. Will this be avoided if I used
remoting (maybe with Binary formatter?)? Alternatively with .Net Web
Services can I provide an interface or otherwise "guarantee" that the
remote methods do not change signature, and get the proxy to compile
once statically like "normal" function calls (I guess it should also
be written to and read from disk instead of a memory cache)? I.e. I
would like to compile once in design time vs multiple times in run
time (each time application starts...).
Thanks,
-- Shaul Dar (sh****@medcon.com)
References:
http://www.dotnet247.com/247referenc...25/128911.aspx
http://groups.google.co.il/groups?l=iw&lr=lang_en|lang_iw&threadm=03bf01c2d7b 1%2494747ac0%24a301280a%40phx.gbl&rnum=1&prev=/groups%3Fhl%3Diw%26lr%3Dlang_en%257Clang_iw%26selm %3D03bf01c2d7b1%252494747ac0%2524a301280a%2540phx. gbl
http://groups.google.co.il/groups?th....phx.gbl#link2
