+1... excellent!
Jeff
On Apr 7, 2009, at 2:59 AM, Julien Vermillard wrote:
Hi
Due to the number of people asking for XMPP support, I can only
welcome
this idea.
After reading a bit of code, some suggestions :
- using mvn ;) since all mina modules & subproject use it
- modularize like Asyncweb in at least two part, one for pojo/codec,
one for the server so you can choose to use only the codec module if
you want to do embed simple xmpp messaging in existing app, look
like
it's enjoyed for http
- even if your code and the packaging is nice and clear, you will
need more javadoc if you want to attract more contributors
Big +1
Julien
Le Tue, 7 Apr 2009 10:32:39 +0200,
Emmanuel Lecharny <[email protected]> a écrit :
Hi Bernd,
you have obviously my full support ! We already have welcomed
FtpServer, which now has 3 committers (congrat Niklas ! Good job !)
and sshd brought by Guillaume Nodet. I think that Vysper will be very
comfortable in this warm MINA place :) I also think that it will help
Vysper to gain visibility (ie, new committers), and will fill a hole
at MINA (many users are asking about how to implement XMPP on top of
MINA)
Wdyt guys ?
On 4/7/09, Bernd Fondermann <[email protected]> wrote:
Hi MINA folks,
Currently I am developing a XMPP[1] server implementation at Apache
Labs[2] called Vysper[3][4] (pronounced 'whisper'). This effort is
going on on and off since 2006, but recently it gained track again
and reached some critical internal milestones (regarding to level
of functionality completed and persistence layer added).
Unfortunately, I am the only contributor to the project until now.
A few days ago at ACEU09 I spoke to Emmanuel and he had the idea of
possibly making Vysper a sub-project of MINA.
Thanks, Emmanuel!
I gave this a few more thoughts and started to like the idea.
So I'm starting a public discussion about it.
The big advantages for Vysper in the MINA community would be:
+ strong protocol related community,
+ feel at home (Vysper uses MINA for IO),
+ ability to have a dedicated ML and make releases (eventually)
+ benefit from on-site MINA know-how
The advantages for MINA could be:
+ add one more emerging protocol to the MINA roster
+ add one more MINA case to the project with specific interesting IO
needs under high load (hint: Twitter),
+ look into optimizing support for non-line-oriented protocols
+ take Vysper (the software, not the project) as a possible
experimental playground, since the IO layer should be relatively
easy to change (for example changing it to MINA 1.x, 2.x, TRUNK).
Any thoughts on this?
Thanks,
Bernd
[1] http://en.wikipedia.org/wiki/XMPP
[2] http://labs.apache.org
[3] http://cwiki.apache.org/confluence/display/labs/vysper
[4] http://svn.apache.org/repos/asf/labs/vysper/
