| Summary: | Add optional cURL network backend support to EFL build system (WebCore only) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Peter Molnar <pmolnar.u-szeged> | ||||
| Component: | WebKit EFL | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED WONTFIX | ||||||
| Severity: | Normal | CC: | commit-queue, galpeter, gyuyoung.kim, gyuyoung.kim, lucas.de.marchi, ossy, rakuco, ryuan.choi | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 124709 | ||||||
| Attachments: |
|
||||||
|
Description
Peter Molnar
2013-11-21 04:08:29 PST
Created attachment 217546 [details]
patch
Is there any benefit when we use cUrl instead of libsoup ? (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. (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. Comment on attachment 217546 [details]
patch
Clear r?, cq? because there is no reply to our questions.
Closing as resolved/wontfix about comments. |