One issue that the WSRX technical committee didn't address in the specification is the persistence of messages. Now, while there were possibly good arguments why that was the case, the reality is that many people want and expect WSRM to provide persistence, and certainly in the case of Sandesha it does. I have long thought that there should be an extension that can be used to signify whether persistence is available and whether it is to be used. This kind of thing is actually common in messaging systems and is available in other messaging specs such as AMQP.
This isn't at all fully baked, but the sort of thing I am thinking of is: 1) A policy element to indicate whether this endpoint supports and/or requires persistence 2) An exchange that happens at create sequence time that indicates whether this sequence should/must be persistent Some questions: * What do people think about this? Is anyone *against* defining this? * If we define this, should we try to standardize it somewhere? Or just treat is as an optional extension. * Any comments on the approach - or suggestions for the actual XML? Regards, Paul -- 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]
