Hello,

libcurl is not a server and cannot listen for HTTP traffic. HTTP
clients are not servers at the same time, they must always request
data. I am pretty sure this is part of the HTTP spec.

If you want data fed on demand you should look at some messaging
service. Jabber or such might suit you needs.

Matt Veenstra
tribalmedia

On Oct 22, 2007, at 2:12 PM, Wiseman, Andrew (Mission Systems) wrote:

> I am just getting oriented to libcurl but have already successfully
> been able to communicate with a web server via your library.
> What I wish to implement using your API is the ability to receive
> asynchronously data being published from a remote host running a
> program built and maintained by another company. It is the usual
> pub/sub paradigm where I (client) first send a subscribe message to
> them (via HTTP) and thereafter, as data becomes available, receive
> it on my side.
> Is the libcurl API designed to support this and, if so, are there
> any sample/example programs that I could use as a starting point
> (as in your example folder)? Or is it that libcurl does not
> support publish-subscribe and I need to go elsewhere. Of course,
> if the latter, can you recommend another product?
>
> Also is there a way to tell libcurl to listen on a specific port
> for incoming HTTP traffic?
>
Received on 2007-10-23