- Original Message -
From: "Dennis Sosnoski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 03, 2003 10:44
Subject: Re: standalone vs. servlet
> Just in passing, one particular area that I suspect causes performance
> problems is the SAX
Steve Loughran wrote:
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.
y high-end app
> server is quite a bit higher.
>
> The first decision you need to make is whether you'd like to develop in Java
> or C++. C++ offers better performance. Java offers huge productivity gains.
>
> Anne
>
> > -Original Message-----
> >
- 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
- Original Message -
From: "Anne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 02, 2003 11:46
Subject: RE: standalone vs. servlet
> Dennis,
>
> I absolutely agree with you regarding application code. Using
well-optimize
e up for schedule delays caused by some nasty memory leak that no
one can find. From my perspective, Java is always my first choice for
language. Go with Java unless you have a compelling reason not to (e.g.,
your processing/memory capacity is fixed).
- Anne
-Original Message-
From: Denni
, Java is always my first choice for
language. Go with Java unless you have a compelling reason not to (e.g.,
your processing/memory capacity is fixed).
- Anne
> -Original Message-
> From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 02, 2003 3:12 PM
, SOAP *platforms* built with C++ run a
lot faster than those built with Java. Just as you won't find a J2EE app
server that can compare with Tuxedo.
Best regards,
Anne
-Original Message-
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 02, 2003 2:18 PM
To: [EMAI
CTED]]
> Sent: Sunday, February 02, 2003 2:18 PM
> To: [EMAIL PROTECTED]
> Subject: Re: standalone vs. servlet
>
>
> Anne Thomas Manes wrote:
>
> >There's no doubt that a C++ environment will offer higher
> performance than a
> >Java environment. Ask Systinet. W
Anne Thomas Manes wrote:
There's no doubt that a C++ environment will offer higher performance than a
Java environment. Ask Systinet. WASP for C++ is a *lot* faster than WASP for
Java. The two environments use basically the same architecture, but C is
just faster than Java. Even so I suspect that
The first decision you need to make is whether you'd like to develop in Java
or C++. C++ offers better performance. Java offers huge productivity gains.
Anne
> -Original Message-
> From: Chuck Musser [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 02, 2003 11:37 AM
> To:
Anne,
Thanks for your response. As you probably suspected, when I said
"native", I meant something written in C, C++ or some other language
that gets compiled to machine code. Things of that nature are obviously
faster, so I guess my question really boiled down to: what are the
advantages of
I'm not sure that I understand what you mean by "native" versus Java. A SOAP
implementation provides language bindings for SOAP. Axis supports Java.
gSOAP supports C or C++. If your application is written in Java, then you
need a SOAP implementation that supports Java. If your application is
writte
13 matches
Mail list logo
