What I wanted to say was we can have a blocking or non-blocking transport with the Synapse Operation Client. So if we make the local transport sender work in a non blocking manner that should be sufficient.
Thanks, Supun.. On Wed, Jan 12, 2011 at 11:47 AM, Amila Suriarachchi <[email protected]> wrote: > > > On Wed, Jan 12, 2011 at 10:32 AM, Supun Kamburugamuva <[email protected]> > wrote: >> >> On Wed, Jan 12, 2011 at 9:10 AM, Amila Suriarachchi <[email protected]> >> wrote: >> > >> > >> > On Tue, Jan 11, 2011 at 5:42 PM, Supun Kamburugamuva <[email protected]> >> > wrote: >> >> >> >> On Tue, Jan 11, 2011 at 8:26 AM, Amila Suriarachchi <[email protected]> >> >> wrote: >> >> > >> >> > >> >> > On Mon, Jan 10, 2011 at 6:41 PM, Heshan Suriyaarachchi >> >> > <[email protected]> >> >> > wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> As you might know, we are having a local transport implementation in >> >> >> Axis2. We are trying to make it available for ESB. Then with the >> >> >> help >> >> >> of >> >> >> this transport; an esb proxy will be able to call a proxy residing >> >> >> in >> >> >> the >> >> >> same esb through the local transport. I have tested the above >> >> >> mentioned >> >> >> scenario with a ESB build and came across some issues. Therefore I >> >> >> need >> >> >> to >> >> >> investigate in to these issues and fix them. I will keep the list >> >> >> updated >> >> >> with the progress. >> >> > >> >> > Axis2 local transport is blocking. So you may need to write a non >> >> > blocking >> >> > local transport with works smoothly with synapse nhttp transport. >> >> >> >> We are trying to improve the existing transport to work in a >> >> non-blocking manner. >> > >> > Well. if you work with Axis2 service client then the transport should be >> > blocking. The same problem we have using >> > service client with nhttp. Better to write a new nlocal transport :). >> > >> >> But from the synapse perspective we have a operation client that can >> handle a non blocking invocation. This is the client that we use for >> nhttp transport. So it should work with a non blocking sender of local >> transport. > > Synapse can use this blocking local transport. That is correct. > > My question is whether it is the correct way or write a non blocking > transport. > > thanks, > Amila. > >> >> Thanks, >> Supun... >> >> > thanks, >> > Amila. >> >> >> >> Thanks, >> >> Supun.. >> >> >> >> > >> >> > thanks, >> >> > Amila. >> >> >> >> >> >> >> >> >> -- >> >> >> Regards, >> >> >> Heshan Suriyaarachchi >> >> >> Software Engineer >> >> >> WSO2 Inc.; http://wso2.com/ >> >> >> >> >> >> Blog: http://heshans.blogspot.com/ >> >> >> >> >> >> _______________________________________________ >> >> >> Carbon-dev mailing list >> >> >> [email protected] >> >> >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> >> >> > >> >> > >> >> > _______________________________________________ >> >> > Carbon-dev mailing list >> >> > [email protected] >> >> > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Supun Kamburugamuva >> >> Technical Lead >> >> WSO2 Inc.; http://wso2.org >> >> E-mail: [email protected]; Mobile: +94 77 431 3585 >> >> Blog: http://supunk.blogspot.com >> >> _______________________________________________ >> >> Carbon-dev mailing list >> >> [email protected] >> >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] >> > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> >> >> >> -- >> Supun Kamburugamuva >> Technical Lead >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 431 3585 >> Blog: http://supunk.blogspot.com >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Kamburugamuva Technical Lead WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com _______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
