Author |
Message
|
sclarke |
Posted: Thu Jun 21, 2007 10:54 am Post subject: WS-ReliableMessaging |
|
|
Apprentice
Joined: 05 Jan 2002 Posts: 39
|
I have a really naive question about WS-ReliableMessaging and obviously don't understand the standard well and yes I can read the standard but I wanted some help. Does WS-ReliableMessaging rely only on http acks or does it/should it use a transport such as mq to make sure the messages get to where they need to go. My architect says no mq involved....
Thanks |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Jun 21, 2007 11:04 am Post subject: |
|
|
Guest
|
Read this: Web Services Reliable Messaging Protocol
(WS-ReliableMessaging)http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-rm/ws-reliablemessaging200502.pdf |
|
Back to top |
|
 |
sclarke |
Posted: Thu Jun 21, 2007 11:28 am Post subject: |
|
|
Apprentice
Joined: 05 Jan 2002 Posts: 39
|
I have previously read this but I am still confused about the implementation. It says the delivery is dependent on delivery assurance which implies to me that the receiver sends an acknowledgement that it got the message and so it implies to me - no mq just acknowledgements (I said I was naive). So if this is the correct understanding, say I run a webservice which sends a message which has information which should only be applied once, the receiver sends the ack but because of network problems, the sender doesn't get that so it raises an error and/or sends again. Does the receiver have to know to not apply that message and wait for the next? This just seems kludgy unless I am completely missing the boat. Does this take mq out of the picture? |
|
Back to top |
|
 |
ourtown |
Posted: Thu Jun 21, 2007 11:33 am Post subject: |
|
|
 Acolyte
Joined: 05 Feb 2002 Posts: 67 Location: Somerset, NJ
|
Web Services Reliable Messaging Protocol is an extension to SOAP and WSDL
>>>>>>>>>>
The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within this specification.
<<<<<<<<<<
It defines the handshakes necessary to deliver messages reliably _________________ Brian S. Crabtree
WBI Consultant |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Jun 21, 2007 11:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The standard appears to describe communications between RM Source and RM Receiver with absolutely no preconceived notions or requirements on what transport those communications are being made across.
It looks like WS-Reliable messages are just XML Documents, like SOAP messages are just XML documents. So you can send those over HTTP as easily as you can dump them in a queue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Jun 21, 2007 12:53 pm Post subject: |
|
|
Guest
|
And reliable messaging implies that the applications at both sending and receiving end must be able to deal with messages not delivered and duplicate messages delivered. |
|
Back to top |
|
 |
|