Re: [RESULT] [VOTE] Apache Mina SSHD 1.6.0

Le 19/09/2017 à 08:26, Jeff MAURY a écrit : > Just noticed while working on the board report that the web site still > advertise 1.2.0 as the latest release Fixed. Thanks Jeff ! -- Emmanuel Lecharny Symas.com directory.apache.org

Re: [RESULT] [VOTE] Apache Mina SSHD 1.6.0

Le 19/09/2017 à 08:26, Jeff MAURY a écrit : > Just noticed while working on the board report that the web site still > advertise 1.2.0 as the latest release That makes me wonder were the previous versions (1.3.0, 1.4.0 and 1.5.0) are stored ? I haven't found them on any repo... -- Emmanuel

Re: [RESULT] [VOTE] Apache Mina SSHD 1.6.0

Just noticed while working on the board report that the web site still advertise 1.2.0 as the latest release Jeff ᐧ On Wed, Jul 5, 2017 at 8:35 AM, Guillaume Nodet wrote: > Closing this vote with 4 +1s and no other votes. > I'll publish the artifacts asap. > > Cheers, >

Re: [RESULT] [VOTE] Apache Mina SSHD 1.6.0

I guess I simply released the nexus repository and forgot to add them to the dist svn site. 2017-09-19 9:25 GMT+02:00 Emmanuel Lécharny : > > > Le 19/09/2017 à 08:26, Jeff MAURY a écrit : > > Just noticed while working on the board report that the web site still > >

Re: MINA3.0 recommended

I forget, does MINA uses the same Processor for both read and write operations? If so, there will never be contention unless you use a Thread Executor Pool in the Filters. If you look at the tests here: https://dzone.com/articles/synchronized-vs-lock You can see that until you really hit > 2

Re: MINA3.0 recommended

I agree that you need to chose the locking mechanism that suits the needs and not necessarily based on benchmarks. I use ReentrantLock in my code because I use Conditions and tryLock(). Ultimately, it doesn't matter what lock the reactor uses because the SocketChannel uses 3 synchronized mutexes

Re: MINA3.0 recommended

Le 19/09/2017 à 15:28, Jonathan Valliere a écrit : > I forget, does MINA uses the same Processor for both read and write > operations? If so, there will never be contention unless you use a Thread > Executor Pool in the Filters. It does. MINA use always the same IoProcessor for one session, to

Re: MINA3.0 recommended

I would add Brian Goetz take on synchronized vs Lock : https://www.ibm.com/developerworks/library/j-jtp10264/ Le 19/09/2017 à 15:28, Jonathan Valliere a écrit : > I forget, does MINA uses the same Processor for both read and write > operations? If so, there will never be contention unless