>> 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
- Comparison of ICAP and SOAP Wanghong Yuan
- Re: Comparison of ICAP and SOAP Mark Nottingham
- Re: Comparison of ICAP and SOAP Lee Rafalow
- Re: Comparison of ICAP and SOAP Roy T. Fielding
- Re: Comparison of ICAP and SOAP Lee Rafalow
- RE: Comparison of ICAP and SOAP Manoj Dhooria
- Re: Comparison of ICAP and SOAP John Martin
- RE: Comparison of ICAP and SOAP Randy Bush
- RE: Comparison of ICAP and SOAP Tomlinson, Gary
- RE: Comparison of ICAP and SOAP Tomlinson, Gary
- RE: Comparison of ICAP and SOAP Bernard Aboba
- Re: Comparison of ICAP and SOAP Brian E Carpenter
- Re: Comparison of ICAP and SOAP Jim Fleming
- Re: Comparison of ICAP and SOAP Mark Nottingham
- Re: Comparison of ICAP and SOAP Michael W. Condry
- Re: Comparison of ICAP and SOAP Mark Nottingham
- Re: Comparison of ICAP and SOAP Michael W. Condry
- RE: Comparison of ICAP and SOAP Hilarie Orman