----- Original Message ----- From: "Anne Thomas Manes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 02, 2003 14:13 Subject: RE: standalone vs. servlet
> I suspect that the use of reflection has a lot to do with the issue. Java > platforms use reflection to enable a bunch of dynamic features which are > really hard to reproduce in a C++ environment. You'll find this to be true > in SOAP platforms, servlet engines, and J2EE servers. It's a trade-off > between function and performance, and in most circumstances , function wins. I think Axis only reflects in the java invocation phase, and in serialisation/deserialisation of stuff. I bet the latter aspect of marshalling is the slowest bit of the process...and wonder how hard it would be to autogen the code to do the binding. > From what I've seen, the two top performing Java SOAP platforms are WASP and > GLUE. BEA and XMLbus are close behind. All of these systems offer > performance comparable to or better than .NET. I'd say that all of these > implementations have been very well designed and optimized. But none of them > can touch the performance of gSOAP, LEIF, or WASP for C++. I'm not sure how > to explain it other than to blame the platform. (Perhaps it's something > inherent to XML processing? There are some functions in which C++ really > excels over Java -- maybe XML processing is one of them.) That'd be a really interesting research paper that would, too bad I dont have the time. Nb, remember, you arent allowed to discuss .net performance or disclose benchmark details :(
