Le Sat, 28 Mar 2009 15:00:18 +0530, Ashish <[email protected]> a écrit :
> > Hi guys, > > > > I just was spending the last 5 days in Amsterdam, during the Apache > > Conference, and had some great time. I also had a talk about MINA > > (I will post the slides on the mina web site, and some great > > conversations with Jean-François Arcand, one of the Grizzly > > committer, who had a talk about NIO 2.0. > > > > During those conversations, an idea popped out of our minds (well, > > beers are the brain's steroids, it seems ...) : what about creating > > a set of standard protocol codec which can be used, alleviating the > > users burden and letting them focus on the handler part ? > > > > That should not be complicated to grow this set of protocol codecs > > (they will be like plugins), and we will get less mails from users > > having problem just because they have made some mistake in their > > decoder. > > > > We may have standard codecs for : > > - http, > > - ldap > > - ntp > > - XML (that is a bit complex, but I have some idea about it) > > - XMPP > > - ... > > > > Wdyt ? > > A big +1 for this. > We can inherit some codecs from ApacheDS, > Was planning to put an XML example in place, just always running out > of time. > > > PS1: Thanks to Ashish's XML sample, I was able to whip this part of > > the presentation in a matter of 30 minutes ! > > Looking forward to see the presentation. > > > PS2 : I just posted this mail in the Thalys, the speed train between > > Amsterdam and Paris. Funny how you can use Wifi when the train is > > running at 300 Km/h !!! And it's free : That's a good old debate... Does de codec is part of the project (ADS, Asyncweb, ...) or can be placed in some MINA's common codec. I think as soon we redo the codec architecture for use only streams & ByteBuffer, we can restart the debate :) Julien
signature.asc
Description: PGP signature
