[Serdev] usrloc loading

[Greger V. Teigre]

Hi Bogdan,
This was an element in a discussion about ser, not openser. I'm not 
interested in having a discussion about openser on serdev beyond 
comparisons that may set ser in some perspective, and I find your 
interruption quite tedious and self-centered. However, if you have 
opinions about ser that are relevant to the discussion, you are welcome 
to join.

If you reread my post, you will see that my argument is that both ser 
and openser make it too easy too create ser.cfgs that break the RFC. 
Quite far from how you read it.

Previous openser/ser discussions on serusers and serdev have not been 
very fruitful, ex. the performance discussions. If you want a dialog for 
the benefit of users or joint development work, feel free to make a 
proposal, but please refrain from self-righteous posts on serusers and 
serdev. You should allow SER users and developers to discuss ser from 
all sorts of perspectives without disturbing with your agenda. This is a 
privilege I believe the openser community enjoys on the openser lists.

Considering that your historical default response in discussions is to 
state your opinion and then be silent, I assume this discussion is dead.

Regards,
Greger

Bogdan-Andrei Iancu wrote:
> Hi Greger,
>
> OpenSER does not "pretend" to be everything to everybody, but tries as 
> much as possible to respond to the user's feedback (reports, needs, etc).
>
> 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.
>
> actually being RFC-compliant is one of the top requirements we have as 
> project and a lot of effort was put in this direction (RFC3261 - 
> correct via building, RFC3263 - complete algh implementation for 
> server discovery, etc)
>
> regards,
> bogdan
>
> Greger V. Teigre wrote:
>
>> :-) In fact, to me, OpenSER seems to pretend that it is all things to 
>> all people. That may work for a while (and in fact, maybe we should 
>> send some people to OpenSER...) 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.
>
>
>