Re: write callback issues (was Re: A new problem)
Date: Tue, 8 Apr 2008 11:25:50 +0200 (CEST)
On Tue, 8 Apr 2008, Prasad J Pandit wrote:
>> libcurl uses recv() to read data from the socket and it will read as much
>> as the OS delivers and then it sends that to the callback as it won't wait
>> for more before it does this.
> In that case, could the trailing new-lines cause my problem?
What trailing newlines and what problem? You're just saying that your write
callback gets called with non-zero length contents. How is that a problem?
>> If you think the recv() call returns too little data you should perhaps
>> debug your IP stack or look to what network setup changes you can do to
>> iprove things.
> I don't see any reason why I should do that; Considering I'm using
> libcurl(as instructed) to do the POST request, and just expect/want the
> proper reply back, that's all.
You get the "reply" back sent to the write callback.
-- Commercial curl and libcurl Technical Support: http://haxx.se/curl.htmlReceived on 2008-04-08