[Serdev] usrloc loading

[Bogdan-Andrei Iancu]

Salut Martin,

Martin Hoffmann wrote:

>>>IMHO, it seems that OpenSER is going 
>>>in the opposite direction of SER by introducing all sorts of "special 
>>>case" functionality that confuses people and allows them to break more 
>>>parts of the RFCs.
>>>      
>>>
>>I know it is your HO, but can you be more specific (just list one or two 
>>cases maybe) where you think OpenSER breaks RFCs?? I always though that 
>>backing up with facts puts more strength in words.
>>    
>>
>
>If you read carefully you will find that Greger wrote "allows [people]
>to break [...] RFCs". This is a well known problem with SER (and hence
>OpenSER) and the actual start of this part of the thread.
>  
>
Greger mentioned "..OpenSER is going in the opposite direction of SER by 
introducing all sorts of 'special case' ..." and  just wanted to know 
exactly what is he referring at....there were a lot of adds-on and maybe 
there are some cases we overlooked and should be fixed.

>Scrolling through the module list of OpenSER I'm not sure if Greger's
>claim is true. The most dangerous or "broken" modules are both in SER
>and OpenSER. I do not know what additional features have been added to
>modules.
>  
>
ok...I see your point...

> 
>  
>
>>actually being RFC-compliant is one of the top requirements we have as 
>>project
>>    
>>
>
>Well, then, at least nathelper, mediaproxy, and parts of uac have to go.
>And textops is high on the list as well.
>
>  
>
all thinks in life are about compromised. If you completely stick to 
what RFCs say, you most probably and up in replacing 80% of the stuff 
you can do from script with a B2BUA..an this is not something positive :).
But does not means the everything in RFCs can be "compromised"...there 
are requirements you cannot go over..

Thanks and regards,
Bogdan