Hi Achintha, Please start looking into the current implementation of Netty-PassThru transport. Few points to consider when you are designing the new transport:
- Decouple transport, protocol and mediation layers. (in the current impl everything is sort of mixed). - Transport code should be reusable in Netty inbond ( have a look at new HTTPCore based PT impl that support inbound HTTP) On Sat, May 9, 2015 at 12:09 AM, Achintha Reemal <rimmyn...@gmail.com> wrote: > As per the initial discussion we had on the GSoC projects related to WSO2 > ESB, We have commenced initial preparations for the project. I have started > reading on different Netty implementations and how Netty operates, as > instructed by the mentors. Final design plan and the architecture, and how > the work should progress would be discussed and finalized with the help of > my mentor in the following week. > > 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 > -- 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 Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
