Hi guys,
Jaliya Ekanayake wrote:
----- Original Message ----- From: "Sanjiva Weerawarana"
That said, there are many areas of Mercury that still require serious
work: threading model, transactions, persistence model etc.. Maybe if
we combine the two and do a new version of Sandesha that'll be better
all around. That is, use Mercury as a source of ideas and code but not
continue "Mercury" in ASF but rather start a new effort to cut-n-paste
stuff from wherever and get a damned good RM impl out to our users.
A big +1 for this.
+1 from me, assuming we can get the cycles from people to make this
happen. Love to hear others' take on this - David? Ant? Amila?
Mercury can remain in wso2.org and we can EOL as the new one comes up
and starts working properly.
+1. Solve our immediate problems now, and also plan for the future we'd
really like to see.
The most important and positive thing I've gotten from this discussion
is that there's a vibrant and caring community around Sandesha. I have
no interest in trying to replicate that elsewhere and fracture this
community.
Well said, sir!
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
