>> I would add one clarification. SOAP encompasses much 
>> broader scope that iCAP. SOAP is a whole architecture for messaging;
> *architecture*?
> it's a simple, lightweight instance of XML use along with a bunch of
> kludged http headers.

hey, don't knock it.  where else can you get remote procedure call,
intermediate proxies which can remove and add message/command content,
and not one whiff of authentication or authorization to pollute it
with silly security ideas?

can you say loaded fusion bomb?

randy

Reply via email to