What do you think of having the two modules (thrift and protobuff) dicrectly at the root of the project and not in a serialization intermediate module ? That would reduce pom hierarchy/maintenance.
Julien On Tue, May 7, 2013 at 9:30 PM, Julien Vermillard <jvermill...@gmail.com> wrote: > Hi, > I just merged your repo, thanks for the contrib ! > If you have any modification to merge, ping us. > > Julien > > On Sun, May 5, 2013 at 12:18 PM, Raphaël Barazzutti > <raphael.barazzu...@gmail.com> wrote: >> Hi Julien, >> >> Thanks for your feedback. >> >> Yes, I splited that features in two sub-modules to avoid people to have >> both dependencies (in most cases they will use only one). >> >> Regards, >> >> Raphaël >> >> >> On Sun, May 5, 2013 at 10:44 AM, Julien Vermillard >> <jvermill...@gmail.com>wrote: >> >>> Hi Raphäel >>> Looks neat, I have definitively a use case for that : RPC. >>> >>> Perhaps we should have two maven module : one for thrift, one for >>> protobuf ? This would avoid people to have thrift dependency when they >>> use protobuff (and "vice versa"). >>> >>> I would be definitively better than the current java serialization >>> codec bothering everybody on android ! >>> >>> Julien >>> >>> >>> On Sun, May 5, 2013 at 1:31 AM, Raphaël Barazzutti >>> <raphael.barazzu...@gmail.com> wrote: >>> > Hi MINA-developers! >>> > >>> > Using extensively MINA 2.0 at my work, I’d like to contribute to the next >>> > MINA version. >>> > >>> > IMHO, MINA 3.0 could provide serialization facilities like Apache Thrift >>> > and Google Protobuf transport. >>> > >>> > According to that I decide to propose the following code to be merged >>> with >>> > the main repository of MINA 3.0. >>> > >>> > Please have a look to my repo : https://github.com/rbarazzutti/mina >>> > >>> > Suggestions are welcome, >>> > >>> > Kind regards, >>> > >>> > Raphaël >>>
