To make the ResourceHandle manageable, move actual HTTP communication tasks into new class which is sub class of CurlHandle.
In the long run, the new class will help to serve NetworkLoadTask for WebKit.
CurlHandle should keep as is because it will be used from other purpose such as WebSocket. That's why the new class is sub class of CurlHandle.
This class must has following features:
- ref counted (to have different life span with ResourceHandle)
- thread safe (to manage background callback and make ResourceHandle work only on main thread)
- can manage curl callbacks internally (to make ResourceHandle simple)
*** Bug 177497 has been marked as a duplicate of this bug. ***
Created attachment 321863 [details]
Created attachment 321866 [details]
Comment on attachment 321866 [details]
Clearing flags on attachment: 321866
Committed r222665: <http://trac.webkit.org/changeset/222665>
All reviewed patches have been landed. Closing bug.