ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Fremantle" <>
Subject Re: [DISCUSS] Mercury Proposal
Date Thu, 12 Jun 2008 12:17:47 GMT

Actually, although Mercury has got a state machine model, I would
personally prefer if we started directly from the State Machine
published in the Appendix of the WSRM1.1 specification, and worked
from here. I think we need two different implementations of a SM - one
for 1.0 and one for 1.1, so we would have to create the equivalent
documentation for 1.0. Amila has a pretty good starting point for the
1.0 SM, and there needs to be some further discussion about exactly
how that should look.


On Thu, Jun 12, 2008 at 5:25 AM, Jaliya Ekanayake <> wrote:
> Hi Paul,
> The proposal starts with a "state machine model" which Mercury has come up
> with.
> So can you give little  bit more details on the state machine model that you
> are suggesting?
> Thanks,
> Jaliya
> ----- Original Message ----- From: "Glen Daniels" <>
> To: "Paul Fremantle" <>
> Cc: <>; <>
> Sent: Wednesday, June 11, 2008 9:53 PM
> Subject: Re: [DISCUSS] Mercury Proposal
>> Hi Paul:
>> Paul Fremantle wrote:
>>> I have posted a proposal here:
>>> Please edit, improve, or discuss.... I put this in the wiki so that it
>>> could be modified.
>> Hm... I thought where we'd ended up discussion-wise was that we would get
>> the Mercury code granted to Apache so that it could be examined / learned
>> from / experimented with, but that we would aim to create a "third way" as
>> the next step for both projects.
>> In other words, the actual work that happens to make the new "unified" RM
>> implementation (whatever it ends up being called) would start with a clean
>> slate and take whatever it can from both Sandesha and Mercury, with the goal
>> of making sure that all the active developers are involved and empowered.
>>  Did I understand that right?
>> Your proposal makes it sound rather like we're going to just start from
>> the existing Mercury code and go from there.
>> --Glen
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair


"Oxygenating the Web Service Platform",

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message