camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Netty consumer fixed message size.
Date Tue, 06 May 2014 11:33:43 GMT
Hi

Its more of a netty question than Camel. You need to use a netty codec
that matches the protcol you use for the data transfer. Is it 100
fixed length, or is it something else. eg how do you know when you got
all the data for a "single message".

There is some out of  the box codec's for fixed length, line
terminator etc codecs that netty/camel supports.

On Tue, May 6, 2014 at 9:08 AM, Cecilio Alvarez
<cecilio.alvarez@hotmail.com> wrote:
> Thanks Claus for your answer.
>
> I'm sure I'm sending blocks of 100 bytes.
> You are right, sometimes is posting to the route two or more of this blocks
> together.
> Is there a way to ensure that each 100 bytes received, the netty component
> will post a new message?
> Or I have to create a custom decoder with a variable length as you
> suggested?
>
> Thanks you in advance.
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Netty-consumer-fixed-message-size-tp5750868p5750895.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Mime
View raw message