Hi,
We need to implement read/write suspend on MINA 3, but I have some
questions.
I understand the usefulness of read suspend :
* controlling slow readers
* blocking incoming message until a long operation completed (like
gathering security information for deciphering/authing the stream)
But fo
It's only loopback tests ? I wonder if the result would be the same on a
real network.
BTW what would be the use case for writing buffer bigger than 64K ? That's
sounding like a waste of memory for me.
On Mon, Jan 14, 2013 at 8:36 AM, Emmanuel Lécharny wrote:
> Hi !
>
> I did some more tests, w
I started refactoring MINA 3 HTTP Codec, but I wonder how to share the
codec infertaces (ProtocolDecoder.class and ProtocolEncoder.class) between
MINA 3 and MINA 2 ? a separate module ?
Because if we don't do that we will finish by having the two version
depending of each other like with the curren
Le 1/14/13 10:47 AM, Julien Vermillard a écrit :
> It's only loopback tests ? I wonder if the result would be the same on a
> real network.
I don't think it would be any different, except that you will exhaust
your 100Mbs bandwith with 1Kb messages before you reach the peak we get
on the loopback,
Le 1/14/13 10:55 AM, Julien Vermillard a écrit :
> I started refactoring MINA 3 HTTP Codec, but I wonder how to share the
> codec infertaces (ProtocolDecoder.class and ProtocolEncoder.class) between
> MINA 3 and MINA 2 ? a separate module ?
> Because if we don't do that we will finish by having the
I wasn't thinking about making MINA 2 Codfec stuff comatible with MINA 3
ones, just wondering how we share the framework independent API.
If you want to use the codec, with.. let's say plain java.net.Socket
blocking stuff. It would be stupid to depend the whole MINA3 core ?
Julien
On Mon, Jan 14
Something like org.apache.commons.codec.Decoder
and org.apache.commons.codec.Encoder but modernized with ByteBuffer /
generics. so you can only depend of this third party jar.
Julien
On Mon, Jan 14, 2013 at 1:26 PM, Julien Vermillard wrote:
> I wasn't thinking about making MINA 2 Codfec stuff co
Le 1/14/13 1:26 PM, Julien Vermillard a écrit :
> I wasn't thinking about making MINA 2 Codfec stuff comatible with MINA 3
> ones, just wondering how we share the framework independent API.
> If you want to use the codec, with.. let's say plain java.net.Socket
> blocking stuff. It would be stupid
[
https://issues.apache.org/jira/browse/SSHD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552791#comment-13552791
]
Andrew C commented on SSHD-203:
---
This should solve my immediate problem (once the git repos ar
On 12 January 2013 17:30, Emmanuel Lécharny wrote:
> Le 1/12/13 11:14 AM, sebb a écrit :
>> On 12 January 2013 07:11, Emmanuel Lécharny wrote:
>>> Le 1/12/13 7:05 AM, Mondain a écrit :
Do I need to pull it from Git or is it still available in SVN?
>>> Definitively from git.
>>>
>>> We can't
10 matches
Mail list logo