RE: [service-orientated-architecture] Re: SOA Reference Architecture

[Guy Crets]

Patrick,   What I mean is: if the sender is unable to transmit message(s) (over HTTP), it will persist the message(s) locally and retry at regular intervals to transmit the message.  The receiver at its end will keep state to filter duplicate messages.   In case of WS-RM (RX), it should be possible to maintain the Sequence and related information on some durable storage mechanism (database, file, ...).  And not only in memory as quite a few WS-RM implementations are doing.   Nice examples of such persistent protocols.are ebMS, RNIF (RosettaNet), EDIINT AS2 and so.  Persistency is unspecified in the WS-RM and WS-ReliableMessaging Policy specs.   Kind regards, Guy Crets   -----Original Message----- From: service-orientated-architecture@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of patrickdlogan Sent: woensdag 28 juni 2006 0:56 To: service-orientated-architecture@yahoogroups.com Subject: [service-orientated-architecture] Re: SOA Reference Architecture > But what we need most, also inside the corporate firewalls, is real > queued (persistent) messaging over HTTP. Could you explain more what you mean by "queued (persistent) messaging"? These terms could have several "nuances". -Patrick __._,_.___ SPONSORED LINKS Computer software Computer aided design software Computer job Soa Service-oriented architecture YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___