[
Lists Home |
Date Index |
Thread Index
]
Hi Len
Len said:
> The market could do as you suggest and flock to SOAP
> based on ease. It wouldn't be the first time. But
> is it the duty of the TAG to warranty an architecture
> based on ease, or should they warranty only the architecture
> designed with 'safety in mind' or whatever criteria are
> chosen? One should as the REST advocates have, explain
> the payoffs clearly. Then and only then can one assess
> the third degree risks if any.
Didier replies:
Yep. If REST architecture could be as much as possible stamped "guru free",
made as simple as possible, then let the demand and supply do the rest (no
pun intented here, Nah... not true that was on purpose :0 ) In any cases,
the payoff should be clear and well grounded in realities. Simple enough
that that in just 30 seconds we can convince somebody in an elevator about
the merits of REST. I know, not easy. Now this time we have just to imagine
a guy opening a laptop, doing a drag and drop operation, writing a single
line of code and bang saying "see, I connected and used a web service". This
guy just showed "ease of use" in a couple of seconds. If, in contrario, we
have to bring the guy to the local "philosophical circle" to discuss the
merits of the technology for 2 hours at the least, then sorry, Len is right,
we've missed the target.
Hint: Economy of bandwith is not a strong argument. Economy of time or money
is. Humans are humans, tell them "what its in it for them" and they'll
repond.
cheers
Didier PH Martin
|
