Timeline for C++ multi-threading demo
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2018 at 9:15 | answer | added | Martin | timeline score: 1 | |
| Jan 5, 2018 at 3:58 | vote | accept | Janith Jeewantha | ||
| Jan 5, 2018 at 3:58 | vote | accept | Janith Jeewantha | ||
| Jan 5, 2018 at 3:58 | |||||
| Jan 4, 2018 at 18:44 | answer | added | Loki Astari | timeline score: 3 | |
| Jan 4, 2018 at 18:11 | comment | added | Loki Astari |
Of course curl will handle multiple simultaneous connections using curl multi handle. This is a much more elegant way of doing it because you can easily handle thousands of network requests on a single thread.
|
|
| Jan 4, 2018 at 16:10 | comment | added | ratchet freak | @Zeta curl makes a copy of every char* that is passed in. | |
| Jan 4, 2018 at 15:54 | comment | added | Janith Jeewantha | I problem never entered my mind. However, the method runs successfully again and again for all the URLs. So I guess the string is copied. | |
| Jan 4, 2018 at 15:06 | comment | added | Zeta |
Does curl_easy_setopt copy the CURLOPT_URL? If it doesn't, the (...).c_str() will get invalid after the line and you end up with a pointer to freed memory.
|
|
| Jan 4, 2018 at 14:40 | answer | added | ratchet freak | timeline score: 5 | |
| Jan 4, 2018 at 12:11 | review | First posts | |||
| Jan 4, 2018 at 12:59 | |||||
| Jan 4, 2018 at 12:07 | history | asked | Janith Jeewantha | CC BY-SA 3.0 |