willem: ping

gertv:pong

pong

willem: I think there might be a problem with the fix for CAMEL-520

willem: it handles an InputStream, but what about all other streaming data (StaxSource, Reader, ...)?

willem: I think we need the logic from the StreamCachingINterceptor instead

gertv: OK, I will dig more about it.

gertv: Please feel free to add your comments on the JIRA.

sure, just wanted to make sure before I did that

BTW StreamCachingInterceptor does not rest the stream cache.

willem: perhaps we should add this to it then

willem: not sure every kind of streaming data allows resetting the stream

you need to reset the inputstream.

I am looking at the StreamCacheConverter.

How can we cache for the Reader?

well, the converter isn't there yet

but it would be almost the same as handling the inputstream or streamsource

how about adding a reset() method to the StreamCache interface?

thinking of it, every kind of StreamCache should allow a reset()

if the data is cached, it can be reset() as well

and we could add the interceptor around the deadletterchannel

and in the deadletterchannel, if the content is a StreamCache, reset() the cache

wdyt?

yeah, and I just find a to do the cache for Reader.

Reader -> String -> Reader

Shall we need to the same thing for the output stream ?

Reader thing sounds fine for me

we probably need a few others as well (Sax/StaxSOurce?)

I don't think we need it for the output stream

OK, I will take care of the {Sax|Stax}Source.

Now, I add void reset() throws IOException; in StreamCache.