synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tishan Dahanayakage (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-929) [GSoC]Netty Transport for Synapse
Date Mon, 29 Apr 2013 15:16:15 GMT


Tishan Dahanayakage commented on SYNAPSE-929:

Hi all, 
I am a final year undergraduate of Department of Computer Science and Engineering, University
of Moratuwa, Sri Lanka. I am familiar with Apache Synapse since during my 7 months internship
at WSO2 Inc. worked on an assignment related to Apache Synapse for over month. Also I am pretty
familiar with SVN and Maven.
I checked out Apache Synapse and started building it. But encountered some errors. I sent
a mail regarding that to Ill walk through samples while debugging
as soon as building is complete. In the meantime I checked out Netty and tried out some tutorials
at here.[1]
Currently I am going through user guide and API to understand the basics.
So as far as I can understand this idea requires an implementation like current nhttp implementation.
High level solution will be, when Netty is enabled a Netty server should be started with a
server handler with proper configurations to handle requests properly. Same server can be
used to receive requests and post responses by using channel concept. Factor would be to deploy
optimal configurations to preserve light weight property of Apache Synapse.
It will be great if I can have some more comments about the idea and some tasks to carry on.
> [GSoC]Netty Transport for Synapse
> ---------------------------------
>                 Key: SYNAPSE-929
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Kasun Indrasiri
>              Labels: gsoc2013
> Netty is a java NIO based client server framework which enables quick and easy development
of network applications such as protocol servers and clients. This should be implement as
a plug-gable transport to Synapse. [1]
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message