[reSIProcate] Unsetting outbound proxy

[Scott Godin]

The point of the unset method is to allow fallthrough to the next profile in
the chain (ie. The profile passed in to the constructor).  If there is no
profile to fallthrough to, then unset doesn't really make sense.

Note:  For many profile settings is doesn't even make sense to 'clear' a
value - ie. The flags.  

The best way to achieve what you want to to set the outbound proxy to an
empty string.  For outbound proxy - this means that it will not be used.

Scott

PS.  I can understand how this would be confusing if you are not using
profile chaining.  Maybe we should consider renaming the methods?  Or have a
UseOutboundProxy setting... 

-----Original Message-----
From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Dmitry
Semyonov
Sent: Thursday, December 29, 2005 5:11 AM
To: resiprocate-devel
Subject: [reSIProcate] Unsetting outbound proxy

Hi.

Quoting Profile.hxx: "If you call an unsetXXXX method on an object with a
NULL BaseProfile it will have no effect."

Therefore, if I use just MasterProfile I can't unset outbound proxy if it
was set once.

I think unsetting should be allowed regardless of BaseProfile value for all
Profile members that are in 'unset' state initially.

--
...Bye..Dmitry.
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel