Danushka I don't agree that Sandesha is at the application level. The WSRM delivery assurances are explicitly NOT at the application level. The acknowledgement that goes back to the sender is an acknowledgement that the WSRM agent has received the message NOT that the application has received the message. Therefore WSRM persistence is about transport level persistence.
Paul On Mon, Jun 16, 2008 at 12:03 PM, Danushka Menikkumbura <[EMAIL PROTECTED]> wrote: > Hi Paul, > I have a couple of questions. > > (a) If we go for something like AMQP, which is at the transport level, we do > not have to couple persistence with Sandesha, which is at the application > level. That means we can make the messages persistent at the transport level > itself. >> >> 1) A policy element to indicate whether this endpoint supports and/or >> requires persistence >> > > (b) Even if we go for transport level persistence, the endpoint does not > have a say in it, because in AMQP we can have either queue level persistence > (i.e. transport receiver level abstraction) or message level persistence > (i.e. message sender level abstraction). >> >> 2) An exchange that happens at create sequence time that indicates >> whether this sequence should/must be persistent >> >> > > Closely relates to my question (a). > > Regards, > > Danushka > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
