David, just to be clear .. the only reason we went down a new impl path is
because we had SUCH a terrible time getting Sandesha to interop over SMTP,
which is a crucial requirement for this customer. SecureRM over SMTP was
just not working out :(.
Sanjiva.
David Illsley wrote:
I think this is a bit of a shame, but you're right that if you've got
a customer you're trying to support you're already a long way beyond
research and experimentation and a Sandehsa2 branch.
Best of luck in filling out Mercury on wso2.org and I'll try to follow
your progress, and hope to see you back here.
David
On Mon, May 5, 2008 at 3:52 PM, Amila Suriarachchi
<[EMAIL PROTECTED]> wrote:
On Mon, May 5, 2008 at 5:34 PM, Chamikara Jayalath <[EMAIL PROTECTED]>
wrote:
Hi Guys,
I also don't see any harm in starting Mercury as a test implementation
under sandesha2. May be we can start it in the scratch area and do a
serious performance comparison in a couple of months. (after Mercury become
rich with the missing pieces David had mentioned).
As I mentioned earlier we have started this as a WSO2 commons project. And
also we have used this one of our customer projects and now we have to add
some improvements for them. On the other hand Synapse and WSO2 ESB has
started to use the Mercury.
So we have hardly any option in keeping Mecury as only a test branch. I
think the possible option is to go ahead as WSO2 Mecury, put all the
Sandesha2 features and consider again this option from another time.
thanks,
Amila.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
