Sorry, but posting a reply does no work (6 hours after the
"successful " post the message is not shown)) so I decided to post it.
This is a reply to a thread
http://groups.google.pl/group/micros...006eaa8e840fd1
Web Service API is a minimal one, there is nothing to refactor. What I
want is to hide complexities of the proxy from third-party
applications using my DLL (not a WS).
Example: I'm exposing a .NET DLL with method UpdateLocalCach e(); it
transparently call some methods from the proxy:
GetFileList() x1
GetFileByName() x N
In this example I don't want the DLL's users to see GetFilexxx methods
(and all proxy additional details, e.g. timeouts, credentails etc.).
Don't get me wrong - I know the WS methods can be used either directly
from user generated proxies or from the web browser... I just don't
want to answer questions/problems like "how should I call the
method...." - and this will come, as developers tend to use
Intellisense withour bothering about documentation (btw, another issue
with the proxy class - it's not documented by default...).
Thanks