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?
I think this is something we should consider pre-1.0.
> 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.
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! :)
I agree in general, but I don't imagine that you think the asynchronous API in Axis2 is one of those mistakes. I think there is a pretty reasonable requirement here. I'm sending a request out and I want the response handled in a certain way. We have that with the proxy services, but not with the general rules. We added it to the proxy services because we needed it. I think we need it in the "main" mediator scenario too. Paul
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]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
