Hi Achintha, As we are behind the schedule, we need to complete the end to end message flow for content aware scenarios. We expect you to finish this by end of this week. If not we won't be able to cover the proposed scope for this project.
On Fri, Jun 26, 2015 at 9:35 PM, Achintha Reemal <[email protected]> wrote: > Hi > > After meeting with Isuru Ranawaka on 25th June, we discussed on the > following proceedings for the coming week. > > - Implement means to read from the queue(while allowing write operations), > which is being currently implemented for the content-non aware scenario. > - Identify means to extract HttpContent once converted into an input > stream, to be fed to mediation. > - Debug and identify the message building implementation, which would > build the message for content aware scenarios. > - Validate the message flow for content aware scenario. > > Regards, > > On Fri, Jun 12, 2015 at 9:05 AM, Achintha Reemal <[email protected]> > wrote: > >> Hi, >> >> After meeting with Isuru on 11th June, we discussed on the following >> proceedings for the coming week. >> >> - Further look into the current implementation with respect to the >> adaptation for with chunking and without chunking in HTTP Content >> - Debug and identify the message flow within the current implementation. >> - Identify how chunked content are being held in the current >> implementation. >> - Research on means to write the chunked content to the current Pipe >> implementation as an input stream, which would enable the content aware >> scenario. >> - Try to implement the above task by 18th June. >> >> Regards, >> >> On Sun, May 24, 2015 at 3:00 PM, Achintha Reemal <[email protected]> >> wrote: >> >>> Hi, >>> >>> During the week, I have looked into the following aspects of the project >>> >>> - Observed the current implementation of Netty-PassThru transport >>> provided by, and special attention was given to the current Pipe >>> implementation as instructed by Isuru. Further observation was done to >>> identify Netty specific parts in the implementation (like the use of >>> classes like ChannelInboundHandlerAdapter, ChannelHandlerContext etc.) >>> >>> - Identifying the usage of different Encoders / Decoders in netty. >>> >>> - Getting to know the current layout of WSO2 ESB transport layer and >>> Mediation Layer, in order to identify the correlation of these two layers, >>> which would be required when decoupling them. >>> >>> Regards, >>> -- >>> *G.H.Achintha Reemal* >>> *BSc Eng Undergraduate| Department of Computer Science & Engineering | >>> University of Moratuwa* >>> *Intern Software Engineer**| WSO2 Lanka (Pvt) Ltd.* >>> *Blog|** rimmythepaperclip.blogspot.com >>> <http://rimmythepaperclip.blogspot.com>* >>> *Twitter|* @rimmynuts(A.Reemal) >>> *LinkedIn|* lk.linkedin.com/in/achinthareemal/ >>> *Mobile| *0715471301 >>> >> >> >> >> -- >> *G.H.Achintha Reemal* >> *BSc Eng Undergraduate| Department of Computer Science & Engineering | >> University of Moratuwa* >> *Intern Software Engineer**| WSO2 Lanka (Pvt) Ltd.* >> *Blog|** rimmythepaperclip.blogspot.com >> <http://rimmythepaperclip.blogspot.com>* >> *Twitter|* @rimmynuts(A.Reemal) >> *LinkedIn|* lk.linkedin.com/in/achinthareemal/ >> *Mobile| *0715471301 >> > > > > -- > *G.H.Achintha Reemal* > *BSc Eng Undergraduate| Department of Computer Science & Engineering | > University of Moratuwa* > *Intern Software Engineer**| WSO2 Lanka (Pvt) Ltd.* > *Blog|** rimmythepaperclip.blogspot.com > <http://rimmythepaperclip.blogspot.com>* > *Twitter|* @rimmynuts(A.Reemal) > *LinkedIn|* lk.linkedin.com/in/achinthareemal/ > *Mobile| *0715471301 > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
