Interesting read. It looks like we consumers of Mina have some work ahead of us if we choose to upgrade.
I would note that keeping the name while changing the API can be a real nuisance for developers who work in a certain way. I copied some example Jersey configuration, which didn't work. I spent days Googling for solutions, finding lots of people apparently succeeding with the same code as mine. Eventually someone on Stack Overflow said "Oh, those are Jersey 1 properties. Jersey 2 is completely different." On Tue, Jul 7, 2015 at 7:05 AM Alexander Christian <[email protected]> wrote: > > > Am 06.07.2015 um 16:43 schrieb Emmanuel Lécharny: > > Le 06/07/15 16:07, Alexander Christian a écrit : > >> > >> And as I understand you right: This should already work with 3.0.0-M2, > >> right? > > Correct. > Great. Then I will try to upgrade to 3.0.0-M2 ... > >> That's fine for people who rely on high-level stuff I guess (don't > >> write theri own protocol). But beside that: Are all/most of the > >> low-level features of mina are working? > > We have not implemented many filters that MINA has : firewall, executor, > > keepalive, statistic, stream... > That's all high-level stuff which I do not use. So that's fine for me > for now. > > > > > >>>> Is there a roadmap to 3.0 release, escpecially w.r.t. time? > >>> No. > >>> > >>> I'd like to find 2 weeks to implement the LDAP codec, which would > >>> require a few more features to be implemented in MINA 3 (demux > handler). > >>> May be this summer ? > >> This summer sounds okay. So I assume that it is a good idea to already > >> use 3.0.0-M2 to adapt to the new api structure? For my new release it > >> would be sufficient if it's "final" end of this year. So "this summer" > >> for 3.0.0 release would fit... > > I didn't say we will release a R.0.0 final this summer, nor by the end > > of this year. It's not how it works here :-) > Ah, now I got it. You tried to say that maybe in summer there's a kind > of roadmap... okay. > > > > The idea is to go with milestones atm. Each milestone should work (ie, > > we don't release if there are some obvious bugs), but it's likely that > > some code and API is going to change before the release. > That's okay for me. As long as the milestones are kind of stable I will > go for it. > > I already started upgrading. Is there an working example for > ProtocolCodec/Filter? mina-examples-3.0.0-M2 seems to only cover > echoclient/server, http, udp and coap. > > br, > Alex > > >
