Re: HTTP Unspecified length

2014-08-27 Thread Claus Ibsen
How much data are we talking about, as you can get the data and then
use the splitter.

On Wed, Aug 27, 2014 at 5:12 PM, Mark Webb elihusma...@gmail.com 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.

 Thank you,
 Mark



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@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/


Re: HTTP Unspecified length

2014-08-27 Thread Mark Webb
It will go on forever.  You connect, send a GET and it streams data to
you.

There are no headers sent.




On Wed, Aug 27, 2014 at 11:22 AM, Claus Ibsen claus.ib...@gmail.com wrote:

 How much data are we talking about, as you can get the data and then
 use the splitter.

 On Wed, Aug 27, 2014 at 5:12 PM, Mark Webb elihusma...@gmail.com 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.
 
  Thank you,
  Mark



 --
 Claus Ibsen
 -
 Red Hat, Inc.
 Email: cib...@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/



Re: HTTP Unspecified length

2014-08-27 Thread Peter Hicks

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



Re: HTTP Unspecified length

2014-08-27 Thread Mark Webb
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