Rex Brooks wrote:
>
>. ..The fact that it anticipates asynchronous
> functionality is IMHO the single most necessary feature for what is
> called web services.
SOAP "anticipates" asynchronous functionality in roughly the same sense
that Unicode does. i.e. it says: "that's not our problem."
I can do that with HTTP also.
> ... Since REST is an architecture and SOAP is
> package wrapper method, are there reasons why SOAP could not fit
> inside REST?
That's what the TAG is trying to do. But it's a little bit like saying:
"object oriented programming is a paradigm and awk is a programming
language. Can't we just use the programming language according to the
paradigm?" You have to address the impedence mismatches.
Paul Prescod
