This does seem like something that could be useful, though I'd imagine it'll be fraught with difficulties in defining the details.
Clearly open standards!=open source, so if we come up with something, finding a standards venue would be a good next step... but that's a bit in the future. I think both parts of your proposal would be needed... a first question if you will.... Any idea on how we define 'persistent'? This must have been gone over lots by other groups that I haven't been involved in. David On Mon, Jun 16, 2008 at 11:26 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
