[asterisk-dev] Peer matching architecture

[Olle E. Johansson]

18 dec 2009 kl. 13.47 skrev Leif Madsen:

> Olle E. Johansson wrote:
>> 17 dec 2009 kl. 19.50 skrev David Vossel:
>> 
>>> ----- "Olle E. Johansson" <oej at edvina.net> wrote:
>>> 
>>>> SIP lovers out there!
>>>> 
>>>> I am still afraid of changing the peer matching too much and what it
>>>> could cause. Therefore I suggest the following:
>>>> 
>>>> - We add a new config option "newdevicematching=yes" and make it
>>>> default to "no" for the next release. Then remove it a release after
>>>> that, since it's no longer "new" :-)
>>> I don't like the idea of creating an option under the assumption it will be removed soon.  I can understand putting code in under the assumption that more efficient implementations may replace it in the future, but in my opinion nothing should go in until it is at least permanent in behavior.
>> 
>> The issue here is that we're going to change behaviour dramatically. In order to be sure that we can be backwards compatible, we need something like this or move to manage two different SIP channels. I think the latter will cost far too much.
> 
> What about just using a different configuration file then, like sip_devices.conf 
> or something to that effect? You could then potentially use both types of 
> matching at the same time (if possible?) which would allow you to perform a 
> migration a bit easier.
> 

Oh, sorry Leif, I missed this mail and had the same idea. Cool stuff, I think at least we Scandinavians are in agreement :-)

/O