Le 5/5/13 7:11 AM, Ashish a écrit :
Folks,
I remember the discussion about not to have CumulativeProtocolDecoder in
3.0. IMHO, we have many scenarios where we would need it, otherwise we
might end up writing our own context implementations to store partial
messages (we have one in
Hi Ashish !
On Sun, May 5, 2013 at 7:11 AM, Ashish paliwalash...@gmail.com wrote:
Folks,
I remember the discussion about not to have CumulativeProtocolDecoder in
3.0. IMHO, we have many scenarios where we would need it, otherwise we
might end up writing our own context implementations to
Le 5/5/13 11:13 AM, Julien Vermillard a écrit :
Hi Ashish !
Do we plan to introduce it 3.0?
I first coded one, but after thinking twice, I start to agree with
Emmanuel here. We should provide facilities for the different use case
:
TLV, pattern matching termination, fixed length
On Sun, May 5, 2013 at 11:43 AM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 5/5/13 7:11 AM, Ashish a écrit :
Folks,
I remember the discussion about not to have CumulativeProtocolDecoder in
3.0. IMHO, we have many scenarios where we would need it, otherwise we
might end up writing
Folks,
I remember the discussion about not to have CumulativeProtocolDecoder in
3.0. IMHO, we have many scenarios where we would need it, otherwise we
might end up writing our own context implementations to store partial
messages (we have one in TextLineDecoder and Http Decoder has its own).
Do
