Hi Venkat. Good.I will look at the implementation and setup a call for discuss next steps.
thanks On Mon, May 30, 2016 at 10:27 AM, Venkat Raman <vraman2...@gmail.com> wrote: > Hi Isuru, > > Good morning :) . Kindly find the 1st week's progress. > > 1) Implementation of Round-Robin algorithm for Outbound Endpoints. > 2) Round-Robin algorithm with group support, but one .iflow config file > can have only one group as of now as mentioned earlier. > 3) Few input validations. > > Kindly find the repo here. > <https://github.com/Venkat2811/product-http-load-balancer> > > In proposal I've mentioned that I'll be covering HTTPS 2nd week,since > it'll be made available later in carbon-gateway-framework repo, I'm > planning to proceed with adding session persistence. > > Will be looking forward for your feedback. > > > > *Thanks,* > *Venkat.* > > On Wed, May 25, 2016 at 8:57 PM, Venkat Raman <vraman2...@gmail.com> > wrote: > >> Hi Ravi, >> >> Thank you for the clear explanation :) . Yes, I added appropriate log >> statements and I was able to understand the flow and I am clear with it >> now. >> >> >> >> >> *Thanks,* >> *Venkat.* >> >> On Wed, May 25, 2016 at 8:09 PM, Ravi Undupitiya <r...@wso2.com> wrote: >> >>> Hi Venkat, >>> >>> Please find answers inline below. >>> >>> On Tue, May 24, 2016 at 9:29 PM, Venkat Raman <vraman2...@gmail.com> >>> wrote: >>>> >>>> >>>> 1) Why are we pushing variables in carbon message variables stack..?? >>>> >>> >>> One of the features of the language is to have variables we can declare >>> and use throughout the mediation flow. We are able to populate variables >>> during loading and during runtime and so variable stack is kept inside the >>> carbon message so each thread has its own variable stack. Hope that >>> clarifies. >>> >>> >>>> 2) Also could you kindly explain how AbstractFlowController and >>>> FlowControllerCallback are working together. My understanding is not quite >>>> clear on this. >>>> >>> >>> AbstractFlowControllers are mediators that require controlling the flow >>> (like filter mediator) where we the mediation flow branching out, in which >>> case we want to mediate only the branch we're in and FlowControllerCallback >>> is a CarbonCallback that we pass on to receive method of mediators of a >>> particular branch. This allows us to continue mediation from the parent >>> once a branch is complete. You can test this out by debugging the >>> FilterMediator, try passing on the usual callback and then check by passing >>> on a FlowControllerCallback. >>> >>> @IsuruR, please correct me if I'm wrong. :) >>> >>> >>> Thanks, >>> -- >>> *Ravi Undupitiya* >>> Senior Software Engineer; WSO2 http://wso2.com >>> >>> >>> *E-mail: r...@wso2.com <http://wso2.com>**M: **+94 772 930 712 >>> <%2B94%C2%A0772%20930%20712>* >>> >>> Lean . Enterprise . Middleware >>> >> >> > -- Best Regards Isuru Ranawaka M: +94714629880 Blog : http://isurur.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
