|
Eric,
A good
start for the multi-protocol question would be to consider SMTP and FTP as 1st
class WS protocols. Just like EDIINT-AS1 and EDIINT-AS3. JMS (and
AMQP) could also serve as a nice reliable transport mechanism. In
particular if we could come up with standard way for describing
FTP/SMTP/JMS bindings and services in WSDL.
The
fact that WS-RM does not fit with other transports lies more with WS-RM.
The synchronous CreateSequence to start the communication and the focus on short
lived sessions don't do much good. When using long lived sequences over a
reliable transport, WS-RM could still add that extra level of end-2-end message
ordering and acknowledgements.
But
what we need most, also inside the corporate firewalls, is real queued
(persistent) messaging over HTTP. WCF (aka Indigo) leaving the
queueing to the MSMQ transport was such a disappointment to
me.
Kind
regards, Guy Crets
__._,_.___
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- RE: [service-orientated-architecture] Re: SOA Reference ... Guy Crets
- [service-orientated-architecture] Re: SOA Reference... patrickdlogan
- RE: [service-orientated-architecture] Re: SOA R... Guy Crets
- [service-orientated-architecture] Re: SOA R... patrickdlogan
- [service-orientated-architecture] Re: SOA Reference... patrickdlogan
- Re: [service-orientated-architecture] Re: SOA Refer... Stefan Tilkov
- [service-orientated-architecture] Re: SOA Refer... patrickdlogan
- Re: [service-orientated-architecture] Re: SOA R... Anne Thomas Manes
- Re: [service-orientated-architecture] Re: SOA Refer... Mark Baker
- Re: [service-orientated-architecture] Re: SOA R... Gregg Wonderly
