bagder: curl-www/libcurl/hiper _schedule.html,1.27,1.28
| Newsgroups | gmane.comp.web.curl.www.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/curl/curl-www/libcurl/hiper In directory labb:/tmp/cvs-serv31423 Modified Files: _schedule.html Log Message: uh, didn't commit the latest... Index: _schedule.html =================================================================== RCS file: /cvsroot/curl/curl-www/libcurl/hiper/_schedule.html,v retrieving revision 1.27 retrieving revision 1.28 diff -u -d -r1.27 -r1.28 --- _schedule.html 7 Jan 2006 22:43:44 -0000 1.27 +++ _schedule.html 11 Jan 2006 07:27:38 -0000 1.28 @@ -34,13 +34,18 @@ <table class="news"> MARKDATE(Jan 7 2006) Sun Yi-Ming's comments also made me realize that we need -to better take care of the socket state for sockets that are used by more than -one easy handle. The "check for socket change" within the multi code currently -doesn't... + to better take care of the socket state for sockets that are used by more + than one easy handle. The "check for socket change" within the multi code + currently doesn't... <p> I've decided to add a <i>curl_multi_setopt</i> function and let that set the -callback function and userp pointer, to better allow the callback to get -called even when easy handles are removed from a multi handle etc. + callback function and userp pointer, to better allow the callback to get + called even when easy handles are removed from a multi handle etc. Hm, that + was even quickly implemented and all code have been adjusted accordingly. +<p> + Now I need to adjust the check-socket-state-changing function to better deal + with easy handle removal and that more than one easy handle may use the same + socket... I'll save that for another day. STOP