RE: [business-transaction] SOAP Bindings Stuff

["WEBBER,JIM (HP-UnitedKingdom,ex1)" <jim_webber@hp.com>]

Mark:

What you say is fine, and actually we're not far off the agreeing (honest).
I've been pushing "pure" RPC to avoid running our own messaging-over-RPC
protocol (i.e. via some "doWork" method). Now if we choose to use SOAP
messages, that's fine. If we choose to use "well behaved" Web Services
(SOAP-RPC plus WSDL), that's fine too. But running one over the other seems
an odd thing to do.

I don't have an ulterior motive here since I <hp-hat-on> can handle either
with the infrastructure I have available </hp-hat-on> and I think that the
"deaf client" problem which RPC seems to get round is significant. As are
the issues of implicitly propagating contexts (say in the SOAP header) and
keeping application-specific data (in the RPC payload in the body) separate.
Most of the common SOAP implementations will provide handle this situation
quite well with relatively little re-jigging.

Jim
--
Dr. James Webber
Hewlett-Packard Arjuna Lab
http://www.arjuna.com