RESOLVED WONTFIX 124710
Add optional cURL network backend support to EFL build system (WebCore only) 
https://bugs.webkit.org/show_bug.cgi?id=124710
Summary Add optional cURL network backend support to EFL build system (WebCore only)
Peter Molnar
Reported 2013-11-21 04:08:29 PST
Add optional cURL network backend support to EFL build system (WebCore only)
Attachments
patch (11.71 KB, patch)
2013-11-21 04:23 PST, Peter Molnar 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Peter Molnar
Comment 1 2013-11-21 04:23:22 PST
Created attachment 217546 [details] patch
Gyuyoung Kim
Comment 2 2013-11-21 20:31:42 PST
Is there any benefit when we use cUrl instead of libsoup ?
Ryuan Choi
Comment 3 2013-11-21 20:59:50 PST
(In reply to comment #2) > Is there any benefit when we use cUrl instead of libsoup ? If we can support libcurl backend well, I believe that we can consolidate network backend because efl used libcurl(backend as ecore-con) as a default. But, If I remember correctly, we dropped to support libcurl backend long time ago because of maintanance issues and lack of functionality. I am not sure whether we can take care of both backends well.
Gyuyoung Kim
Comment 4 2013-11-21 21:07:49 PST
(In reply to comment #3) > (In reply to comment #2) > > Is there any benefit when we use cUrl instead of libsoup ? > > If we can support libcurl backend well, I believe that we can consolidate network backend because efl used libcurl(backend as ecore-con) as a default. > > But, If I remember correctly, we dropped to support libcurl backend long time ago because of maintanance issues and lack of functionality. Yes, right. I remember Eric wanted to remove libcurl backend if no ports used it. I agree to use ecore-con instead of libsoup. However, I don't like to increase maintenance overhead if there is no benefit on using cUrl.
Gyuyoung Kim
Comment 5 2014-02-09 21:21:12 PST
Comment on attachment 217546 [details] patch Clear r?, cq? because there is no reply to our questions.
Csaba Osztrogonác
Comment 6 2014-09-15 04:09:00 PDT
Closing as resolved/wontfix about comments.
Note You need to log in before you can comment on or make changes to this bug.