Le 07/07/15 13:22, Alexander Christian a écrit : > > > Am 07.07.2015 um 12:34 schrieb Emmanuel Lécharny: >> There is one in the mina-coap sub-project. You can also have a look at >> the mina-http and mina-http2 codec (also mina-protobuf and mina-thrift). >> >> Of course, they are not samples, but tehy are full-fetured >> implementation of the Encoder/Decoder interfaces. > Thanks. I will look into this. >> >>> The question is: How was it developed if there is no example? Maybe >>> the example is not that nice and clean, but no example at all: Seems >>> you're completely lost. >>> As the class names and the concept are (slightly) >>> different/undocumented, it's very hard to find out how to do it right. >> I agree. For us, it was easy : we had Mina 2 to look at. But, yes, we >> need real-world samples in a separate project, *and* some documentation. > Sure, for you guys who wrote that stuff it was easy ;-) > btw: The MINA git repo is also available on github. Is it possible to > fork the project on github, work on some parts (documentation etc.) > and create pull-request that you guys then review and merge? Or do I > have to do it all via the official apache git repo?
Whatever works for you. I think the github repo is catching upp anyway, so that should be ok. That's the good thing swith git : everything could be a repo... Note that it would be good to create a JIRA for any pull-request, otherwise it might be lost on the mailing list. </snip> > But MINA 3 currently seems to be a pain. >>> Of course I could become a commiter and push the current >>> developmentspeed a bit. But I'm busy with my library that currently >>> uses MINA.... >> That is the crux of the problem : if everybody expect that someone else >> will work on MINA, it won't move very fast. I'm not complaining about >> this situation, but I'm asking you to try to understand why we are >> slow :-) > I completely understand. But I don't think that this will change in > future. It's the same with every other OSS... I'm not that pessimistic. MINA didn't get a lot of traction lately, but I think that's quite nromal for a low level project, which has already reach one stable state. It's hard for new commers to jump into a train which is already running and working. I would expect that a rewriting would bring more attention... > > Personally, my intention to work in my open source library is: Its THE > solution for my software-problem. So I work on it and improve it, so > that the result is getting bigger and better. I made the lib open > source, so that others can benefit from my work (GPL). So I don't do > it for others. Actually I do it for me. Actually, MINA is critical for me, as it's the base for Apache Directory. My next task on my schedule would be to migrate ApacheDS to MINA 3. So, yes, it's a side project, but a critical one. > And if other's want to make money, the have to pay license fees (dual > licensed). That does not create a big income. But from time to time I > can wine and dine with my wife. I must admit I don't make money with MINA, but I don't complain :-)
