hi all:I am using multi socket,however , I am confused with this API,
int timer_callback(CURLM *multi,/* multi handle */
long timeout_ms, /* see above */
void *userp);/* private callback pointer */
CURLMcode curl_multi_setopt(CURLM *handle,
On Mon, 5 Jan 2015, Marc Hörsken wrote:
Do we have any strategy to resolve such issues on x64 /
64-bit builds?
Yes - to fix 'em ;-)
In all seriousness, I've not looked at these particular issues yet - I've been
trying to minimise the warnings in the main curl and libcurl source code and
On Fri, 2 Jan 2015, Prash Dush wrote:
Does libCurl support NTLM with FIPS mode enabled on Linux machines.?
Why don't you just try it and see if it works?
--
/ daniel.haxx.se
---
List admin:
On Mon, 5 Jan 2015, 兰天 wrote:
CURLMcode curl_multi_setopt(CURLM *handle, CURLMOPT_TIMERFUNCTION,
timer_callback);
and I know that when the timeout changed,the callback function are called,
however,the first time we register the callback function ,for example:
curl_multi_setopt(handle,
Hiya Marc,
On Mon, 5 Jan 2015, Marc Hörsken wrote:
Yes - to fix 'em ;-)
okay, so I will just go ahead and try to fix some of them one after
another. ;-)
If we can - I think it would be worth it.
If we are doing things like int... or long len = strlen(string); then we
should be using the
Hi Steve,
If we can - I think it would be worth it.
If we are doing things like int... or long len = strlen(string); then we
should be using the right type.
If these sort of warnings are as a result of the values being passed into
curl functions that accept long parameters, for example
thanks for replying.
before the first time callback function called ,at this time,we do not know the
timeout time,right? so how could value timeout changed,and how could callback
function called?
In the example file hiperfifo.c , the first time callback function
timer_cbcalled,and in that
Hi Steve,
Do we have any strategy to resolve such issues on x64 /
64-bit builds?
Yes - to fix 'em ;-)
okay, so I will just go ahead and try to fix some of them one after another. ;-)
In all seriousness, I've not looked at these particular issues yet - I've
been trying to minimise the
Hello everyone,
I would like to bring the following high number of conversion warnings during
64-bit compilation for Windows to your attention:
1464 warnings:
http://curlbuild.uxnr.de/builders/curl_winssl_cross_x64/builds/2620/steps/testcurl/logs/warnings%20%281464%29
