On 18.01.2007, at 18:56, Gregg Wonderly wrote:
Okay I'll state this again just to see if you're still not
convinced. RMI/JERI
is a uniform interface. There is exactly one operation, "INVOKE".
That's all
there is. The mapping of application operations on the parameters,
to software
system components is automatically done for you at software compile
time,
instead of being done by after market tools that might take an XML
schema and
create a Object mapping for you for example.
In SOAP, the description of the invocation layer is done in the
XML. In
RMI/JERI it is done in Java, and the compiler provides all the
information that
the endpoint and invocation handler need to map language based
operations onto
operations related to the service endpoint.
That's my argument about how HTTP is not really new in this
regard. HTTP has
more operations, because it wants to have a service layer that is
not part of
the users application.
The difference is that HTTP is an application interface. It is the
interface of the user's application.
When you buy a book at Amazon, the application interface you are
using is HTTP.
Jan
With RMI/JERI, that service layer is part of your
application so that you don't have to buy something and install it
separately
from your service/client. You just run your software, and it
already has all
the features needed to be a "service".
