which is the best soap implementation?

[siddharth aggarwal <si...@rediffmail.com>]

Hi,
 I have heard about other soap imlpementations like:-
1) microsoft toolkit
2) idoox wasp

what are the performance issues involved in choice of implementation. I need some real fast transfer between a client and server and so is it advisable to use an interpreted language like Java (in case of the apache implementation)? If there is something better than apache then are there issues such as not being freeware etc. ?
Please give me your suggestions.

Regards,
Siddharth.

On Tue, 11 Sep 2001 Gopinadh Bandaru wrote :
>the best solution is go for axis (apache soap3.0).It is 
>4 times faster than
>apache soap2.x.
>The major chage was they are using sax parser instead 
>of dom it makes to
>take less memory and increases 
>the prerformance.
>
>
>cheers
>gopi
>
>
>
>
>
>-----Original Message-----
>From: siddharth aggarwal [mailto:sidaggarwal@rediffmail.-
>com]
>Sent: 11 September 2001 07:02
>To: soap-dev@xml.apache.org
>Subject: problem making choice of soap implementation
>
>
>Hi,
> I want to send a stream of words from a client to a 
>server. The server
>processes this stream of words and sends back 1 or more 
>xml documents (i
>think this could be done by concatenating the xml 
>documents and then
>converting it all to one string). The client then needs 
>to process these xml
>documents (each of these documents could have a 
>different format, unknown to
>the client).
>
>I am facing the following problem:-
>
>1) Should I use soap based messaging or RPC?
>2) Is the apache implementation of SOAP too slow to 
>perform such a task
>(i.e. frquent transfer of large amounts of data between 
>machines)?
>
>Please advise me?
>Regards,
>Siddharth.
>
> 
>
>