On 01 Jul 2015, at 14:17, Juha Heinanen jh@tutpro.com wrote:
Olle E. Johansson writes:
I can either keep it as http_query() with the same name and remove it from utils, or change the name to something else, like http_query_plus or http_query_ng, to avoid collissions.
since http_query would be in another module, i would like to keep the existing one in order to avoid changes in config files.
why don't you put your curl stuff in existing utils module rather than introduce a new one? if that is not ok, you could use your curl module api in utils module to implement your version of http_query.
Ok, I'll keep it in utils.
I am hoping we can develop an API to make sure all modules that use CURL use one CURL library binding. When we have that, we can convert http_query too.
I'll just rename my current version to something else while waiting for the API to be developed.
Daniel Stenberg points me in that unified APi usage when discussing binding to CURL from many modules in a multiprocess app. He wasn't too happy over us linking many modules to the CURL library.
/O