[EFL] Drop support for the Curl network backend.
Created attachment 125647 [details] Patch
Comment on attachment 125647 [details] Patch Attachment 125647 [details] did not pass efl-ews (efl): Output: http://queues.webkit.org/results/11432332
I wanna decide to remove this libcurl support after profiling libcurl. The result will be updated soon.
Comment on attachment 125647 [details] Patch I'm happy to rubber-stamp this, except it seems to break the efl-ews.
Please make sure to follow-up by removing the actual curl support files if EFL was the last client of curl.
(In reply to comment #5) > Please make sure to follow-up by removing the actual curl support files if EFL > was the last client of curl. The WinCairo port seems to use cURL. The other network backend used by the Windows port is CFNetwork, which still seems to be proprietary.
Created attachment 126431 [details] Patch for landing
If many guys agree on removing curl port from WebCore, I also agree with this removal. But, I'm still wanna decide this removal after libcurl performance profiling in EFL port. I was told that the performance profiling result will be reported by next week.
I did comparing loading test with libsoup and libcurl last week. Total test site number is 96 and our test result is below. Average : libsoup 4.93sec libcurl 5.51sec Libcurl is better than libsoup just in case of 6 sites. Libcurl's performance is not better. These are our test results. Thank you.
(In reply to comment #9) > I did comparing loading test with libsoup and libcurl last week. > Total test site number is 96 and > our test result is below. > Average : > libsoup 4.93sec > libcurl 5.51sec > Libcurl is better than libsoup just in case of 6 sites. > Libcurl's performance is not better. > These are our test results. > Thank you. OK, thanks. For posterity, it would be good to know more about the methodology of these tests (ie. what exactly was tested and how).
Committed r107562: <http://trac.webkit.org/changeset/107562>
OK. We added test codes for page logging loading time including some exception handling. If we start browser app. then it read the url lists for test and memorize loading start time each url loading start. When the loading is finished for one site, loading time is calculated and automatically start loading next url. For using these methods, we tested about 96 urls each 6 times. Each Libcurl and Libsoup devices are started loading synchronously. (actually a little term is exist) Thank you.