Although ewebkit used libsoup internally, it's not good for EFL developers to use it.
Created attachment 224022 [details] Patch
Created attachment 224023 [details] Patch
Comment on attachment 224023 [details] Patch Basically, I agree not to open libsoup header in ewk header. However, it would be good to replace those APIs with new wrapper APIs together.
(In reply to comment #3) > (From update of attachment 224023 [details]) > Basically, I agree not to open libsoup header in ewk header. However, it would be good to replace those APIs with new wrapper APIs together. Basically, I think that it is wrong approach to expose session directly. In my opinion, we'd better to expose proper APIs like ewk_view_proxy_uri_set instead of exposing setter/getter of session and letting application developers learn extra libraries.
(In reply to comment #4) > (In reply to comment #3) > > (From update of attachment 224023 [details] [details]) > > Basically, I agree not to open libsoup header in ewk header. However, it would be good to replace those APIs with new wrapper APIs together. > > Basically, I think that it is wrong approach to expose session directly. > > In my opinion, we'd better to expose proper APIs like ewk_view_proxy_uri_set instead of exposing setter/getter of session and letting application developers learn extra libraries. Yes, I meant that it is nice to remove those APIs with new wrapper APIs together.
Comment on attachment 224023 [details] Patch As we talked, we believe that this APIs aren't being used now. So, let's remove it. r=me.
Comment on attachment 224023 [details] Patch Thanks.
Comment on attachment 224023 [details] Patch Clearing flags on attachment: 224023 Committed r164028: <http://trac.webkit.org/changeset/164028>
All reviewed patches have been landed. Closing bug.