function, this is only meant to allow easier tracking of the internal handle's
state and what sockets they use. Only for research and development.

to a multi stack will cause CURLM_BAD_EASY_HANDLE to get returned.

supported

and while doing so it became apparent that the current timeout system for
the socket API really was a bit awkward since it become quite some work to
be sure we have the correct timeout set.

Jeff then provided the new CURLMOPT_TIMERFUNCTION that is yet another
callback the app can set to get to know when the general timeout time
changes and thus for an application like hiperfifo.c it makes everything a
lot easier and nicer. There's a CURLMOPT_TIMERDATA option too of course in
good old libcurl tradition.

API with glib2

with multi interface and pipelining. This test just works and did not repeat
the problem his test code showed, but could still serve as a useful test.

anymore

case 535 and it now runs fine. Again a problem with the pipelining code not
taking all possible (error) conditions into account.

In this way 304 tests out of 304 reported OK.

make sure that a previously used one is killed first (since they re-use the
same .pid file etc)

now runs fine.

but that worked nicely in 7.15.5. I converted it into test case 532 and
fixed the problem.

transfer support