GitLab

Do not print error, instead raise an exception that need to be caught.
The calling method will then decide if the error should be displayed or
not.

Fix regression inserted with 8cba1a31

Use an underscore '_' in front of the function name.

All the options are now stored in an object.

When using a literal IP address, the IP address is sent as SNI.
This may lead to a `close notify' from the server. Therefore we
decided to catch the OpenSSL error and suggest to use the --nosni
option.

When using multistreams, requests are sent in parallel. curl keeps
track of different time values for each handle independently. This
means that we can retrieve the transfer duration for each handle
separatly.
It is then possible to calculate the average time taken by each
transfer independently. Even so this might be an interesting data to
compute, this does not reflect the benefits of using parallelism.
Therefore the average time taken by a request is calculate as the
total time elapsed to perform all the requests divided by the number
of transfers.

When using curl multi, we populate the multi with handles and then
call multi_perform which leads to curl establishing the multi
connection and sending tranfers once it is done. This looks
satfisfying enough if we don't look at the time values stored by curl
in each handles. In this case it appears that all the transfer time
are set to the time the curl multi was started meaning that all
transfers keep track of the connection time, this is normal for the
first transfer but unnecessary for all the following ones.

Therefore by sending a first transfer asking for the root NS, it
allows to open the connection without populating the resolver cache.
And thus keeps the curl timers more accurate.

The OK/KO output was reserved for the --check option. When using
--pipelining it could be nice to say if it succeed or fail (at
this point success only means that all the queries got an answer
in the given time window)