If you are using gSOAP today on Windows to talk to web services or build a web service in native code, you should be able to switch to use WWSAPI right away. Give a try and if you see any issues or have comments, please let us know using forums, http://social.msdn.microsoft.com/Forums/en-us/wwsapi/threads/
Thanks for bringing this scenario to our attention. In design of the API, we have focused on C/C++ developers. You are right that it should be possible to build COM wrapper around the API to make it available to VB6. This can be an interesting CodePlex project useful for many VB6 developers. As for out of the box support for VB6, this is not in our plans at this moment.
You should be able to use WWSAPI instead of gSOAP for talking to WCF services. If you see any problems, please let me know. You can use either feedback form on my blog,http://blogs.msdn.com/nikolad, or post on WWS API forum, http://social.msdn.microsoft.com/Forums/en-US/wwsapi/threads/.
First, I am sorry for a delay in the reply. I will try to address your comments one by one. Please feel free to ask more questions. I would be happy to answer them for you.
- Why another API?
- This API helps developers who use native C/C++ code to connect this code to web services. There is not any other solution support by Microsoft for this task and this has been very often request from developers. Alternative solution is to build WCF service and interop into native code. However the performance of such solution is pretty bad and in many cases this solution is not acceptable. This is why WWSAPI was created and it provides much better performing solution for this scenario.
- Will this API replace RPC? How it compares to RPC?
- No, WEb services API does not replace RPC. These API target different scenarios and meet different needs. In our performance runs, RPC based solutions tend to be faster than WWSAPI based solution both on HTTP and TCP channel and binary encoding. However the performance difference between these too solutions is expected and acceptable.
- Open this project as open source project?
- There are no plans of opening the source code of this API.
- Will API available down level?
- Yes, our plan to make this API available down level to Windows XP, Vista, Server 2003 and Server 2008 pre-R2. The API runtime DLL will be installed on on all flavors of Windows 7 and Windows Server 2008 R2 out of the box .
- Is this just client API or is there server side also?
- There are both client and server side APIs and it is possible to build both clients to web services and web services.
- What is the relation of a server side of the API to Http API?
- Not sure what this question is about exactly. If service is set to use HTTP channel binding, the implementation of Web Services API is going to use Http.sys, however developer does not need to use http.sys directly.
I hope this reply answers your questions. Please feel free to ask more. You may also use contact form from my blog http://blogs.msdn.com/nikolad/ to contact me offline later on.
- Why another API?