AW: [Feature Enhancement] Camel body size

2013-11-24 Thread jhm
> Von: Claus Ibsen [mailto:claus.ib...@gmail.com] > > Though I like the idea if we could get some sort of API in Camel > components that optionally could determine the message size. So we > could keep track of a size of message data in and out. > > Sorta like an activity monitor tool, such as TCP

Re: AW: [Feature Enhancement] Camel body size

2013-11-24 Thread Claus Ibsen
Hi Yeah as people have said here. I think its hard to implement an expression/logic in camel-core, that supports all kinds of messages bodies/headers/properties/attachments and whatnot that is possible out there. Also it gets trickier when you work with streams, as you would need to access the to

Re: AW: [Feature Enhancement] Camel body size

2013-11-23 Thread Hadrian Zbarcea
So that's one way of doing it. I assume you'd want that customized to include headers or not, right? Now how's that different than having an expression (actually any number of specialized expressions), returning the size calculated using your algorithm of choice. Set your header of choice with

AW: [Feature Enhancement] Camel body size

2013-11-23 Thread jhm
Store the object in a byte array and count the bytes? Jan > -Ursprüngliche Nachricht- > Von: Hadrian Zbarcea [mailto:hzbar...@gmail.com] > Gesendet: Samstag, 23. November 2013 20:00 > An: users@camel.apache.org > Betreff: Re: [Feature Enhancement] Camel body size > > I wonder how you'd i

AW: [Feature Enhancement] Camel body size

2013-11-23 Thread jhm
When only asking the body for its length you lose the length of properties, headers and attachements. (Especially when retrieving emails the last could be big ;) Jan > -Ursprüngliche Nachricht- > Von: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Gesendet: Samstag, 23. November 2013 1