Hi Anne, thank you for the information. I guess we will have to stick to xmlrpc for the time being then
cheers, Tom Anne Thomas Manes wrote: > Tom, > > You can find an extensive list of SOAP implementations at > http://www.soapware.org/directory/4/implementations. It lists about a dozen > implementations that support C and/or C++. (81 total imlpementations!) > > I'm not aware of any SOAP implementations that support asynchronous calls > yet. Systinet will add support for asynchronous calls in the next release of > WASP Server for Java. The beta should be available in January. The product > already supports JMS as a transport, so you can simulate an asynchronous > call right now, but you would have to poll for results. The new asynchronous > API will support callbacks and other asynchronous features. > > You can build C and C++ clients and servers for Windows and Linux using WASP > Server for C++. WASP Server for C++ doesn't support the asynchronous API > yet, but we plan to add support for this feature in the future. WASP Server > (both Java and C++) interoperates easily with other SOAP systems, such as > .NET, Apache SOAP, Apache Axis, and others. All WASP products are free for > development and testing purposes. Lightweight versions of WASP Server > (called WASP Lite) are free for commercial use. Sources are available for > WASP Lite for C++. For more information about WASP products, please visit > www.systinet.com. > > As for SOAP versus XML-RPC: SOAP offers more capabilities, more services, > and more extensibility that XML-RPC. SOAP has also been more widely adopted > by the industry, and W3C is defining an XML Protocol standard based on SOAP. > If your goal is to link applications within your own private community and > you don't need the extensibility features of SOAP, then I'd say that XML-RPC > is probably sufficient for your needs -- and it's certainly much simpler > than SOAP. But if you intend to use an XML protocol for interoperability in > a wider, less controlled community, SOAP would probably be better. You'll > find many more businesses interested in using SOAP, primarily because SOAP > supplies the extensibility capabilities to support attachments, security, > reliability, routing, transactions, workflow, and more. These extensions > will become critical when people start using Web Services to conduct serious > business that involves billing and payments and reliability. > > Best regards, > > AnneThomas Manes > CTO, Systinet (formerly Idoox) > www.systinet.com
