We currently are doing our best to stablize our API before we reach the first RC. The API is pretty stable even now, but we will have to see what new requirements kick in. Anyhow, the API change won't be massive enough to make anyone get screwed up.
So, if you are under way of refactoring a project, I'd suggest you to try the trunk. HTH, Trustin On Dec 13, 2007 4:47 AM, mclovis <[EMAIL PROTECTED]> wrote: > > > > mclovis wrote: > > > > We currently have NIO server code working based on our own current > > design. Looking at the Mina code we feel we could simplify things somewhat > > by switching to Mina. We are also currently in a refactoring phase. That > > being said it looks like you will release Mina2 -M1 soon and have promised > > GA by summer. In your opinion, could we refactor to Mina1 for production > > quality and later upgrade with some changes to Mina2 , or wait to M2. If > > we are going to refactor using Mina in the near future, now is the time > > for us. I am posting this trying gain some understanding of Mina1 to Mina2 > > features as well as compatibility. Any insights will be appreciated. > > > > If there are any code committers following this thread any insights from > them would also be appreciated. > > -- > View this message in context: > http://www.nabble.com/Mina-1-vs-Mina-2-current-tp14296037s16868p14302489.html > > Sent from the Apache MINA Support Forum mailing list archive at Nabble.com. > > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
