You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Sanjiva Weerawarana <sa...@watson.ibm.com> on 2001/12/05 15:06:26 UTC
C++ impl of a SOAP client library
Hi guys,
I've been working with a group of volunteers in Sri Lanka to
build a C++ SOAP client library. We're just about done with a
first cut and are ready to commit the code ...
This code is not a complete SOAP stack; its only a client-side
library. Its not anywhere as powerful as the Axis architecture
in terms of the potential, but its a start.
However, it appears that Systinet is now ready to offer their
C++ impl as well. I'd like some advice on how to proceed!
One possibility is to separate a client library from a complete
SOAP stack. OTOH a complete stack includes a client library.
Sanjiva.
Re: C++ impl of a SOAP client library
Posted by Radovan Janecek <ja...@systinet.com>.
Hi Sanjiva,
I think that we can commit both codes under /c directory and try to start
the merging process asap. (e.g. /c/client for your client, /c/wasp for WASP)
What do you think?
WASP for C++ is smaller (about 1 MB of sources) and younger than Java one -
thus more flexible :-). Sources of this version of WASP will be available on
our web site within two weeks.
Radovan
Radovan Janecek
VP, Engineering, Systinet (formerly Idoox)
http://www.systinet.com
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: "Axis Development List" <ax...@xml.apache.org>
Sent: Wednesday, December 05, 2001 3:06 PM
Subject: C++ impl of a SOAP client library
> Hi guys,
>
> I've been working with a group of volunteers in Sri Lanka to
> build a C++ SOAP client library. We're just about done with a
> first cut and are ready to commit the code ...
>
> This code is not a complete SOAP stack; its only a client-side
> library. Its not anywhere as powerful as the Axis architecture
> in terms of the potential, but its a start.
>
> However, it appears that Systinet is now ready to offer their
> C++ impl as well. I'd like some advice on how to proceed!
>
> One possibility is to separate a client library from a complete
> SOAP stack. OTOH a complete stack includes a client library.
>
> Sanjiva.
>