cpp-netlib-devel

[cpp-netlib-devel] Asynchronous client-request response body

[Max M. <ma...@kt...>]

Hi everybody,

Perhaps I've missed some vital information or link, but it seems to difficult to find any extensive documentation at all about the specific capabilities of the cpp-netlib, so I guess I'll go ahead and ask here and either you can help me directly, post a link to extensive documentation, or ignore.

I've already viewed http://cpp-netlib.github.com/reference_http_response.html#response-concept and http://cpp-netlib.github.com/reference_http_client.html.

I'm trying to use the cpp-netlib to forward live http streams, such as when broadcasting from a webcam or similar, so I am trying to use both the server and client components asynchronously. As far as I can see, this is working fine for the server.

However, when it comes to the asynchronous client, I would like to do this:

client::request clientRequest(reqUrl);
client::response clientResponse;
clientResponse = clnt.get(clientRequest);
strtype result;
while(!(result = clientResponse.body()).empty())
	{
		std::cout << result << std::endl;
		connection->write(boost::make_iterator_range(result));
	}

Idiomatically this is pretty easy to understand, assuming that clientResponse.body() returns the bytes already read from the response, and that empty returns true when no more bytes can be read.

This does not work (but I thought it was worth a try when I had no idea about the implementation ;) )

Is it possible with the current API to simulate this behaviour? I saw an issue about implementing client streams, but I thought, it can't hurt to ask?

Thanks for your time.

Best regards, Max Malmgren

Re: [cpp-netlib-devel] Asynchronous client-request response body

[Dean M. B. <mik...@gm...>]

On Fri, Jan 21, 2011 at 11:59 PM, Max Malmgren <ma...@kt...> wrote:
>
> I'm trying to use the cpp-netlib to forward live http streams, such as when broadcasting from a webcam or similar, so I am trying to use both the server and client components asynchronously. As far as I can see, this is working fine for the server.
>
> However, when it comes to the asynchronous client, I would like to do this:
>
[snip]
>
> Is it possible with the current API to simulate this behaviour? I saw an issue about implementing client streams, but I thought, it can't hurt to ask?
>

Unfortunately, it's not possible to do that at the moment. Supporting
streaming from the client is something I fully intend to implement,
when I do get the time to do it.

At the moment I've been preoccupied with paid work to be able to
devote enough time to this.

> Thanks for your time.
>

I'm sorry it's not possible to do this yet, but I assure you it's up
there in the list of things for me to fix.

(Or maybe if others had the time to do it, maybe that might happen sooner :) ).

-- 
Dean Michael Berris
about.me/deanberris