On 25.02.2007, at 22:55, Eric Newcomer wrote:
Jan,
In that case I would expect WebSphere MQ to be compatible with the
Web since it has a uniform interface. Correct?
Messaging systems have a uniform interface[1], yes. I am not sure
what you mean by 'compatible' though. Messaging systems are a
different kind of architectural style than the Style of the Web is.
Following one of REST's constraints doesn't make a style the REST
style. The Pipe and Filter style (e.g. Unix shells) for example
employes a uniform interface, too. But that style is not the Web
style either.
Do massaging systems constrain the messages to be self descriptive
(do they require the payload to be of standardized formats)? Message
self-descriptiveness is also one of the very important one of REST's
constraints.
Jan
[1] You can of course also abuse those to tunnel commands
Eric
----- Original Message ----
From: Jan Algermissen <[EMAIL PROTECTED]>
To: [email protected]
Sent: Sunday, February 25, 2007 2:53:27 PM
Subject: Re: [service-orientated-architecture] SOA Pizza Order
Surprises
Eric,
your posting 'deserves' a more detailed reply, so sorry for only
sending a short comment (I still have a pile of work on my desk for
tonight).
On 25.02.2007, at 18:23, Eric Newcomer wrote:
It is just hard to believe that the lack of uniform interfaces in
SOAP and WSDL is the cause of all the disconnect with the Web.
The lack of a uniform interface (the plural doesn't really make
sense here, does it?) is contrary to the architectural style of the
Web. That is just an undebatable
fact. An architecture that does not employ a uniform interface can
never be of the REST style and an architecture that does not
specifically constrain itself to
HTTP's set of methods on all objects is necessarily disconnected
from the Web.
Jan
(And, yes, GET /foo/lauchMissile is not HTTP's GET, it is tunneling
the launchMissile invocation through GET)
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
