I would try to keep http prefix for all the functions that do not overlap. I expect the functions from utils modules will be moved to one of the new http client modules in the future, given the better framework provided by these ones.
For the ones that overlap and don't provide (or target) the same functionality, then maybe something new can be found.
For the ones that overlap in functionality and target, until the old ones get merged, then we can use some other prefix, but I think http should be full in there, maybe http_curl_ or httpc_ -- again, in the plan should be merging the functions from utils into these ones in the near future, ending up in having full set of cunctions prefixed with http_.
Cheers, Daniel
On 03/02/16 10:56, Olle E. Johansson wrote:
I am about to rename functions with the “curl” prefix as well as the connection defintions.
Since the old function in utils use “http” as a prefix we need something else.
“http_client” seems too long
“hc” and “hac” for sync and async functions may work. “httpcon” instead of “curlcon”.
Any better ideas?
/O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev