[sr-dev] db libraries

Olle E. Johansson oej at edvina.net
Thu Dec 20 17:35:01 CET 2012


20 dec 2012 kl. 17:20 skrev Daniel-Constantin Mierla <miconda at gmail.com>:

> 
> On 12/20/12 5:16 PM, Olle E. Johansson wrote:
>> 20 dec 2012 kl. 16:13 skrev Ovidiu Sas <osas at voipembedded.com>:
>> 
>>> On Thu, Dec 20, 2012 at 9:39 AM, Daniel-Constantin Mierla
>>> <miconda at gmail.com> wrote:
>>>>>> - nathelper - some extra functionality, not sure if can be kept
>>>>>> completely
>>>>> Maybe Andreas can look into this, as there is a lot of work going on with
>>>>> nathelper and the new rtpproxy anyways.
>>>> I think Ovidiu Sas looked at it when he split the rtpproxy out in a
>>>> dedicated module.
>>> IIRC, ping_contact whas the extra functionality in nathelper:
>>> http://sip-router.org/docbook/sip-router/branch/master/modules_s/nathelper/nathelper.html#ping_contact
>>> I don't know how widely used is this functionality.
>>> 
>>> Maybe we should have a separate thread per module (in user mailing
>>> list to gather more imput) and see if it's worth merging the code or
>>> use only the k version.
>>> 
>>> 
>>> Also, on a separate note, I saw the we have a few db2_[module].
>>> I think it would make sense for these modules to rename them into
>>> [module]_db[1|2].
>>> For example: ldap - we should have both versions under modules:
>>> - ldap_db1
>>> - ldap_db2
>>> Just a suggestion ...
>> What's the difference between the db1 and db2 interface?
> It is not the case here, modules_k/ldap does not have any relation to database interface.
Well, I changed the issue then - I'm curious on the difference...

/O


More information about the sr-dev mailing list