SOAP/BizTALK = solution for TR&P? Not yet! (was: issue from 20 Ju lycon-call)

["Eckenfels. Bernd" <B.Eckenfels@seeburger.de>]

Hello,

> This all depends upon whether you consider SOAP as a
> packaging solution or as a message (payload). A SOAP
> message as payload is currently supported in the TR&P
> architecture.

Since MS will merge BizTalk and SOAP 2.0 in the future SOAP can handle
the Routing/Enveloping of messages (at least as limited as MS thinks it
is important). Therefore SOAP/BizTalk is trying to solve the same
problems as TR&P.

So the question is, if the Framework from MS will be sufficient. At
least in neighter the BizTalk 1.1 nor the SOAP Specification carry all
the Elements used and needed in current messaging infrastructures. I
made a comment regarding this a few month ago on the BizTalk list. It is
stuff like "alternate address shemes", "next hop routing",
"hop-recording for loop prevention", "return receipt, dsn, message-id,
..."... some of the issues may be resolved by SOAP, since it can handle
transactions, some others are still missing.

So i expect the TR&P ppl only to use SOAP/BizTalk if they can improve
the Ideas from MS to a more general scope. It is still too limited to
HTTP direct communication. (Which is not yet possible or sensible
everywhere... for example: how do u run a HTTP Post Acceptor on a dislup
line?).

Greetings
SEEBURGER AG
Bernd Eckenfels
-- 
SEEBURGER AG, Edisonstrasse 1, D-75015 Bretten, Germany
Fax:+49(0)7252 96-2222 Fon:+49(0)7252 96-1256 http://www.seeburger.de/