Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Wed, 9 Apr 2008 16:26:04 +0200
From: Kristian Rink <kristian@zimmer428.net>
To: users@tomcat.apache.org
Subject: Re: Why use SOAP in Java
Message-ID: <20080409162604.786f7dc4@n428>
In-Reply-To: <335933.76457.qm@web45716.mail.sp1.yahoo.com>
References: <335933.76457.qm@web45716.mail.sp1.yahoo.com>
Organization: kaum
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Am Wed, 9 Apr 2008 07:21:29 -0700 (PDT)
schrieb Sam Wun <samwun2@yahoo.com>:

> I am wondering why use SOAP with Java?
> Since SOAP is based on RPC, I think the best question may be asked,
> why use RPC for client-server application?

Well... let's put it another way: Why not use SOAP and/or RPC for
client-server applications? Isn't RMI per definition also sort of RPC
if you keep it "straight" Java? Good thing about doing RPC in a
SOAP-like way is that you virtually can create a client-server system
without requiring any of the both parts to be implemented in Java, as
it is easy to, say, call server-sided Java "procedures" from a system
implemented in Python, .NET, Perl or whatever could come to your mind...

Cheers,
Kristian

-- 
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@jabber.ccc.de * icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org