As a bandaid approach, I'm using wget along with netcat to a Camel Netty endpoint. It's working for now :)
On Wed, Aug 27, 2014 at 1:50 PM, Peter Hicks <peter.hi...@poggs.co.uk> wrote: > Hi Mark > > > On 27/08/14 16:12, Mark Webb wrote: > >> I would like to pull data from a webserver has an unknown length. I send >> the server a GET command and it sends data continuously, each record on a >> separate line. I would like each record in a separate Camel exchange. >> Not >> sure if this is allowed in the HTTP spec, but the server does this. >> >> Is there a way to handle this using a Camel endpoint? This could be done >> using a custom Netty handler, but I'd rather use and existing component. >> > This appears similar to something I posted about a while ago at > http://camel.465427.n5.nabble.com/Processing-data-from-a- > long-lived-HTTP-streaming-URL-td5753758.html - but I never found a > solution to it. > > > Peter > >
