Search…
README
How to read this book
The cURL project
Network and protocols
Install curl
Source code
Build curl
Command line basics
Using curl
HTTP with curl
FTP with curl
Using libcurl
HTTP with libcurl
Bindings
libcurl internals
Easy handles and connections
Everything is multi
State machines
Protocol handler
Backends
Windows vs Unix
Memory debugging
Content Encoding
Structs
Resolving host names
Index
Powered By GitBook
State machines
To facilitate non-blocking behavior all through, the curl source is full of state machines. Work on as much data as there is and drive the state machine to where it can go based on what's available and allow the functions to continue from that point later on when more data arrives that then might drive the state machine further.
There are such states in many different levels for a given transfer and the code for each particular protocol may have its own set of state machines.

mstate

One of the primary states is the main transfer "mode" the easy handle holds, which says if the current transfer is resolving, waiting for a resolve, connecting, waiting for a connect, issuing a request, doing a transfer etc (see the CURLMstate enum in lib/multihandle.h). Every transfer done with libcurl has an associated easy handle and every easy handle will exercise that state machine.
The image below shows all states and possible state transitions. See further explanation below.
libcurl transfer state machine
All transfers start in INIT and they end in MSGSENT
yellow: the initial setting-up states
blue: resolving names and setting up the connection
green: initiating and setting up the transfer
white: the transfer
red: post-transfer
All states within the striped area have an associated connection.
Previous
Everything is multi
Next
Protocol handler
Last modified 7mo ago
Export as PDF
Copy link
Edit on GitHub