Glen. I didn't think there was any consensus from the previous
discussion (does the word dissensus exist?) :)
I am actually pretty happy to do either, I think each approach has +s and -s.
On the side of starting from the Mercury codebase, Amila has got it to
a point where it satisfies the 1.0 spec, including Replay.
On the other hand, Mercury doesn't yet implement 1.1 or
MakeConnection, and also it doesn't support transactions yet, so there
are some fairly large aspects still to be coded. And starting afresh
might well get more involvement from the wider community which I think
has been the main pushback on this proposal so far.
I guess one open question is - who is willing to put in the effort to
work on this?! If it's just Amila, then starting afresh won't be much
benefit, because he will be happier to keep working from the code he
has already built. If there is a wider set of people willing to put in
effort, then starting afresh might have significant benefits.
Paul
On Thu, Jun 12, 2008 at 2:53 AM, Glen Daniels wrote:
> Hi Paul:
>
> Paul Fremantle wrote:
>>
>> I have posted a proposal here:
>> http://wiki.apache.org/ws/FrontPage/ws-sandesha/MercuryProposal
>>
>> 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
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org