User Tools

Site Tools


devel:libcurl_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
devel:libcurl_integration [2016/01/28 20:55]
hugh.waite [Requirements]
devel:libcurl_integration [2016/02/03 11:04] (current)
oej [Discussion]
Line 32: Line 32:
 The final solution will be a combination of these, however consensus should be reached on the architecture. The final solution will be a combination of these, however consensus should be reached on the architecture.
 Should these be combined into a single module, or should one depend on the other? Should these be combined into a single module, or should one depend on the other?
-It should of course be easy to understand and use.+It should of course be easy to understand by the end user. 
 + 
 +Items to discuss: 
 +  * Name of modules(s) 
 +  * Definition of API functions and parameters 
 +  * Use of worker pools 
 + 
 +Names 
 +  * The curl module has been renamed to "Http_client" 
 +  * Need new name for the new module
  
 Please add your own comments below (hpw) Please add your own comments below (hpw)
 +
 +  * (gv) I think it was mentioned at the meeting in Brussels: it would be nice to have a separate configuration file with the "connections", which can be reloaded at run time (like http://kamailio.org/docs/modules/stable/modules/tls.html#tls.r.tls.reload).
 +  * (oej) The "curl" prefix needs to go away from the functions, parameters and api in the http_client module. New names discussed on sr-dev
devel/libcurl_integration.1454010921.txt.gz · Last modified: 2016/01/28 20:55 by hugh.waite