Pankaj is right.  It is Apache AXIS client side code.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 23, 2002 2:32 PM
Subject: RE: Hi


>
> Pankaj,
>
> I'm sure that when you checked with HP's legal compliance they approved of
> your comments...
>
> I did not see any mention on the website that HPs implemenation uses the
> Axis client side code - surely the Axis team deserve some credit?
>
> Charlie
>
>
>
>
>
> [EMAIL PROTECTED] on 23/04/2002 13:12:01
>
> Please respond to [EMAIL PROTECTED]
>
> To:    [EMAIL PROTECTED]
> cc:
> Subject:    RE: Hi
>
>
> > -----Original Message-----
> > From: Deepth Dinesan [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, April 23, 2002 4:31 AM
> >
> > How does AXIS compare with Suns Web Services developer pack ? in terms
> > of
> > - SOAP compliance
> > - Performance
>
> This is an axis mailing list so I may not be welcome presenting my views :
> -)
>
> However, in my simple tests ( like get and echo of an int array ) on the
> same machine, I have found Sun's JAX-RPC RI implementation to be faster
> than
> Axis. I had conducted these tests with Axis-alpha3 and JAX-RPC EA2 on my
> Athlon900Mz machine running Windows2000 with Sun's JDK1.3.1.
>
> It wouldn't be fair to state the figures but if Axis community is
> interested, I could share my benchmark programs.
>
> > - (Any known implementations ? )
>
> HP ( My employer ) has a SOAP imploementation that uses Axis client side
> code and adds more functionality such as XML-DSig, SOAP-SEC, SOAP over
SMTP
> etc. You can find more about it at
> http://www.hpmiddleware.com/products/hp_web_services/default.htm
>
> Regards,
> Pankaj Kumar
>
>
>
>
>
>
>
> This communication is for informational purposes only.  It is not intended
as
> an offer or solicitation for the purchase or sale of any financial
instrument
> or as an official confirmation of any transaction. All market prices, data
> and other information are not warranted as to completeness or accuracy and
> are subject to change without notice. Any comments or statements made
herein
> do not necessarily reflect those of J.P. Morgan Chase & Co., its
> subsidiaries and affiliates.
>

Reply via email to