C++ Wrapper

Question

It is cool. But I think having C++ wrappers for it would be nice and useful.
I really like to see more in native development world in windows .

Thanks,

Answer 1

Hello,

Thanks for the feedback. We are not planning to provide C++ wrappers in Windows 7 time frame. We will evaluate the need for C++ wrappers when we start planning the future versions of the API.

Thanks,
Nikola

---

Nikola Dudar is the Program Manager for Windows Web Services API team. This post is provided "AS IS" with no warranties, and confer no rights. Use of any samples is subject to the terms specified at http://www.microsoft.com/ info/cpyright.htm

Answer 2

I realize Microsoft has chosen to reduce support for COM clients such as VB6 and VBScript, but a COM wrapper might help make WWSAPI a decent alternative to the aging (and unsupported) SOAP Toolkit as well.

Just a thought.

Answer 3

Hi Bob,

If I read you post right, you are basically asking for COM-based C++ APIs over WWSAPI. Am I right? Or is there anything else in SOAP toolkit that you would need to see in WWSAPI to consider it as a good alternative?

Thanks,

Nikola

---

Nikola Dudar is the Program Manager for Windows Web Services API team. This post is provided "AS IS" with no warranties, and confer no rights. Use of any samples is subject to the terms specified at http://www.microsoft.com/ info/cpyright.htm

Answer 4

Sorry to be so late getting back here Nikola,

Yes, I think COM-based APIs are what I was asking for as long as the interfaces could be used without too much difficulty from traditional COM clients like VB6, VFP, VBScript, etc.  That may require some careful consideration of data types, providing enumeration interfaces and such though.

I would think that fully supporting several programming and scripting tools could be a challenge.  My immediate interest is in VB6.  The issue I see is a need to be able to "compile" WSDL into target host source, i.e. VB6 Classes.  Much as you can generate *.wsdl.h files for C/C++ now.

Thank you for your reply,

Bob

Answer 5

Hi Bob,

Thanks of the feedback! We will consider this scenario also when we start talking about C++ programming model for this API.

Thanks,
Nikola

---

Nikola Dudar is the Program Manager for Windows Web Services API team. This post is provided "AS IS" with no warranties, and confer no rights. Use of any samples is subject to the terms specified at http://www.microsoft.com/ info/cpyright.htm

Answer 6

Any updates on the status of the wrapper? Do you have an ETA?  Thanks.

Answer 7

Could you please explain better what do you mean by C++ wrapper?

Answer 8

The API of WWS is in pure 'C', not in C++. Many C++ books say that C++ is a better 'C' and I agree with that, so I think that is the reason of the initial request.
In C++ you can use string types (similar to C#), the powerful STL library and encapsulate many WWSAPI C lines into C++ classes and methods to be reused later in many other C++ programs. All the resources I mentioned reduce development times dramatically and the performance is not affected so much.
I say not so much because one little disadvantage I see is the consuming time in conversion of char types, arrays of chars, structs with chars, etc into the C++ world and viceversa.
Hope it helped.

---

Paparipote

Answer 9

Thanks all for suggestions! I am not ready yet to discuss our plans for C++ version of the API. Once we have more concrete plans and design ideas, I will definitely share those with everyone on my blog.

---

Nikola Dudar is the Program Manager for Windows Web Services API team. This post is provided "AS IS" with no warranties, and confer no rights. Use of any samples is subject to the terms specified at http://www.microsoft.com/ info/cpyright.htm

Answer 10

The API of WWS is in pure 'C', not in C++. Many C++ books say that C++ is a better 'C' and I agree with that, so I think that is the reason of the initial request.
In C++ you can use string types (similar to C#), the powerful STL library and encapsulate many WWSAPI C lines into C++ classes and methods to be reused later in many other C++ programs. All the resources I mentioned reduce development times dramatically and the performance is not affected so much.
I say not so much because one little disadvantage I see is the consuming time in conversion of char types, arrays of chars, structs with chars, etc into the C++ world and viceversa.
Hope it helped.

---

Paparipote

I believe a pure 'C' is better solution performancewise. Assuming the main reason for WWSAPI is 

native Windows solution, this is more than enough to begin with. 

I suppose C++ will consume more resources to be developed. 

From my point of view what is important for WWSAPI is more architectural 

and migrational - in other post I expressed my personal opinion about REST, IIS, Web.Config, End Points.

These were crystalized from dealing with actual customers.