Skip to content
  1. Aug 09, 2018
  2. Aug 08, 2018
  3. Aug 07, 2018
  4. Aug 03, 2018
  5. Aug 02, 2018
  6. Aug 01, 2018
  7. Jul 31, 2018
  8. Jul 30, 2018
  9. Jul 29, 2018
  10. Jul 28, 2018
  11. Jul 26, 2018
    • Darío Hereñú's avatar
      docs/INSTALL.md: minor formatting fixes · 7212c4cd
      Darío Hereñú authored
      Closes #2794
      7212c4cd
    • Christopher Head's avatar
      docs/CURLOPT_URL: fix indentation · 812d05da
      Christopher Head authored
      The statement, “The application does not have to keep the string around
      after setting this option,” appears to be indented under the RTMP
      paragraph. It actually applies to all protocols, not just RTMP.
      Eliminate the extra indentation.
      
      Closes #2788
      812d05da
    • Christopher Head's avatar
      docs/CURLOPT_WRITEFUNCTION: size is always 1 · 9526cbe6
      Christopher Head authored
      For compatibility with `fwrite`, the `CURLOPT_WRITEFUNCTION` callback is
      passed two `size_t` parameters which, when multiplied, designate the
      number of bytes of data passed in. In practice, CURL always sets the
      first parameter (`size`) to 1.
      
      This practice is also enshrined in documentation and cannot be changed
      in future. The documentation states that the default callback is
      `fwrite`, which means `fwrite` must be a suitable function for this
      purpose. However, the documentation also states that the callback must
      return the number of *bytes* it successfully handled, whereas ISO C
      `fwrite` returns the number of items (each of size `size`) which it
      wrote. The only way these numbers can be equal is if `size` is 1.
      
      Since `size` is 1 and can never be changed in future anyway, document
      that fact explicitly and let users rely on it.
      
      Closes #2787
      9526cbe6