-----------------------------------------------------------
Victor Coustenoble
KXEN Integration & Support
mailto:[EMAIL PROTECTED]
Tel : 33 (0)1 41 44 94 76
http://www.kxen.com
-----Message d'origine-----
De : Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
Envoyé : mardi 18 décembre 2001 17:51
À : [EMAIL PROTECTED]
Objet : RE: asynchronous calls and more
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
> -----Original Message-----
> From: Tom Caljon [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 18, 2001 3:55 AM
> To: soap-user
> Subject: asynchronous calls and more
>
>
> Hi,
>
> We need :
> - a rpc server that supports asynchronous calls. Preferably written
> in Java so that we can easily use JMS
> The rpc server should support multiple asynchronous calls all at
> the same time (so that clients don't continuously have to poll for new
> messages)
> - a number of rpc clients that are capable of working with this rpc
> server, sometimes performing asynchronous calls
> We would like to have C++ (and C) clients for Windows and Linux
> Is the apache soap server capable of this, and do such clients exist?
> If not, does anyone have any pointers to software that is?
>
> The apache xmlrpc server/client support asynchrounous calls. Writing a
> C++ xmlrpc library (which we did) is a hell of a lot easier than a soap
> library, so what would be the main reasons not to prefer xmlrpc over soap?
>
> thanks a lot,
> Tom
>
