Paul Fremantle wrote:
Ruwan
There is no point in doing the continue, because you can always follow
up the <send/> with a <drop/>.
As regards outSequence I don't agree with Sanjiva :-)
You disagree that its implementable later as an augmentation of what we
have now, or you disagree with my view that it should be done later?
This seems so similar to the things we've done in Axis2 for
nonBlocking calls that I think its a useful addition. I'm +1 unless it
delays our 1.0.
My experience has always been that when we go beyond real requirements we
end up hurting ourselves; its *always* possible to create fictitious
requirements of course ("imagine a scenario where ..."). Axis2 has several
things I'd like to retract but its too late now. I'm trying to find a way
to avoid that .. so just because Axis2 has made mistakes that's no reason
to repeat it! :)
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
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]
