Re: WebSocket support for Axis2
Deepal Jayasinghe <[email protected]>
| Newsgroups | gmane.text.xml.axis.user |
|---|---|
| Message-ID | <[email protected]> |
IMO, rather than adding new features it is better to fix some of the pending issues (there are many). Since Gihan has already done a GSoC project he should be familiar with the project, so he can fix issues and help the open source community. AFAIK Google's intention is to bring *new *people to open source community via GSoC. Deepal > On Mon, Mar 17, 2014 at 9:29 PM, Gihan Madushanka <[email protected]> wrote: >> Hi All, >> >> I'm Gihan Madushanka an undergraduate and also a participant of the GSoC >> 2013 programme. This year also I look forward to participate this >> programme. Few weeks ago I contacted a mentor and received few possible >> project ideas. Among them I like to implement the idea of WebSocket >> transport support for Axis2 as my project of this year. I spent last few >> days to do the basic research and draft initial project proposal. >> >> According to my research I found that one of the following frameworks can be >> used to provide WebSocket transport support for Axis2 and these frameworks >> also can be further categorized into two types as annotation based and >> not-annotation based. I'm much thankfull if Axis2 developers can review and >> help me to identify best framework for my project. >> >> >> Annotation based frameworks >> >> https://github.com/Atmosphere/atmosphere >> >> https://tyrus.java.net/ > IMO it's better to use JSR-356 a.k.a "Java API for WebSocket" to > define server/client WebSocket endpoints so that they can be deploy on > WebSocket supported containers such as Tomcat or can use framework > like Tyrus to run through standalone Axis2 server. Please note > supporting to WebSocket containers is equally important as supporting > to standalone server you may develop this as two modules so that > standalone server module will use only required. > > I haven't use Atmosphere so I can't compare it with Tyrus but AFAIK > Atmosphere still depends on their proprietary annotations instead of > JSR-356 so I would much prefer for Tyrus here. > > BTW, have you create JIRA issue for this ? > > [1] - https://jcp.org/en/jsr/detail?id=356 > > Thanks ! > > >> >> >> Non-annotation based framework >> >> https://github.com/TooTallNate/Java-WebSocket >> >> http://www.eclipse.org/jetty/documentation/current/jetty-websocket-client-api.html >> >> >> Regards, >> >> Gihan > > -- Blog - http://blogs.deepal.org/