Re: Best Way to communicate with Tomcat
Re: Best Way to communicate with Tomcat
- Subject: Re: Best Way to communicate with Tomcat
- From: Mike Schrag <email@hidden>
- Date: Wed, 17 May 2006 09:46:23 -0400
Having a second server running doesn't seem like it would effect
EFFICIENCY ... From my experience, I would say SOAP is EASIER than
RMI for the reasons he listed, but more efficient? Not sure about
that. Binary serialization from an over-the-wire standpoint is going
to be WAY smaller than the equivalent enormous XML SOAP message. The
big question is the cost of Java serialization compared to that of
SOAP "serialization" of the object. This is something you'd have to
benchmark to really know for sure, but given that you custom
implement Serialization as well to tune it, I have to believe RMI
would totally win that race. But under heavy load, I really don't
know ... You have a battle-hardened Apache + WO, but taking the hit
of XML parsing vs whatever impl of an RMI server you chose to use,
which probably isn't nearly as tuned as Apache OR WO, but it doesn't
have the XML parsing overhead.
If performance is a concern, I wouldn't take anyone's word for it, I
would just setup both scenarios and find out with your own exact
situation.
But if you're looking for "get it working pretty quickly," then I
would definitely go SOAP. RMI is just a pain to deal with -- just my
two cents.
ms
On May 17, 2006, at 5:10 AM, Philippe Lafoucrière wrote:
On 16 mai 06, at 22:34, email@hidden wrote:
Hello Philippe;
Perhaps you could expand on what you mean by "interconnect" as
this is like saying you want to build a bridge without specifiying
if it's for two cars a day, for or a motorway or for rail. In
each case it would be a different sort of bridge you would want.
Andrew, sorry for the lack of info... The webservices will use some
fonctionnalities of the WO cluster for several part of the webapps.
Buying something on the webapp should invoke the WO part which is
responsible of managing the account, contact the bank, etc. This
could led to an important (but not huge).
btw, Michael answered me (off list) :
"I would recommend using SOAP to communicate with an application on
a Tomcat server. I believe the performance of SOAP requests/
responses is actually more efficient than RMI because you do not
have the overhead of requiring another server process running. I'm
not sure if you know, but to utilize RMI, you must have one of the
components registered within an RMI server process, and the client
must query the RMI server to obtain a connection to the service.
The SOAP method is much more direct in that your data is serialized
into XML datatypes and deserialized much like making an remote
method call. The only trick is ensuring the data you are
transferring can be serialized and deserialized."
I think SOAP can be a solution since it sounds easy to implement in
WO too.
Thank you
Philippe
--
Philippe Lafoucrière
C.T.O
Mobile : +33 (0)6.89.54.49.62
KAMAYO
Interactive Solutions
66, Ave de Landshut
Centre de Transert
BP 50149
60201 Compiègne Cedex - France
Tel : +33 (0)3.44.36.70.48
Fax : +33 (0)3.44.30.21.03
www.kamayo.com
***
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden