SOAP is kind of interesting stuff...
and there' s lot of similar interesting approaches out there
(mostly driven by EAI needs).
Sure it will make your life easier for a lot of
situations,
but I do not think that it will replace RMI/IIOP
or CORBA where robustness/scalability/availability
load balancing & failover are not a plus.
Regarding SOAP have a look at:
http://www.xml.com/pub/2000/02/09/feature/index.html
cheers.
Simone Fiorini
-----Messaggio originale-----
Da: Ted Neward [mailto:[EMAIL PROTECTED]]
Inviato: giovedì 17 febbraio 2000 12.36
A: Orion-Interest
Oggetto: Re: Some Advice Requested.
>We will rewrite our applications with a method we call servlet-entities :
>HTTP as a protocol replacing RMI/IIOP
>XML for data exchange
>
Don't forget to have a look at SOAP--it's exactly what you're describing
above.
Ted Neward
Java Instructor, DevelopMentor ( http://www.develop.com )
http://www.javageeks.com/~tneward
-----Original Message-----
From: Jan Hendrickx <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Date: Monday, February 14, 2000 1:58 AM
Subject: RE: Some Advice Requested.
>Hi Folks
>
>I share Darrens opinion completely.
>
>EJB is a 'nice' thing but ...
>
>- Compared to Servlets with DB access using a connection pool, performance
>is a disaster
>(response times from less then 10 ms (using servletexec on IIS, i'm sorry)
> to more than 0.5s (Orion))
>
>- memory load increased by 500% for the same application
>
>- network load increases in some cases by 1000% (fine grained components)
>
>- and last but not least, i know that 0.91 stands for 'not completed yet',
>robustness is not up to a production level yet.
>
>- Not only Orion EJB, but also SunEJB, Websphere Pro3, Pramati EJB are, to
>my opinion, not up to the task yet.
>
>We stopped (the company), for now on investigating EJB. (Untill
>implementations have improved)
>
>We will rewrite our applications with a method we call servlet-entities :
>HTTP as a protocol replacing RMI/IIOP
>XML for data exchange
>
