< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

RE: [reSIProcate] Re: [reSIProcate-commit] COMMIT: resiprocate 5978sgodin: - fixed nasty cut-and-paste bug in AclStore - db forAcl's now working


Ah right - I see.  I needed access to the TlsPeerName stored in the TlsConnection object.  What if instead we set the TlsPeerName in a new field in the message - maybe in the security attributes? 
 
Rohan and I quickly discussed this - and he was concerned about increasing the size of the SipMessage for people that may not be interested in Peer Name - but I still think this option is nice and clean and definately more efficient for repro to lookup.  Is anyone opposed to this?
 
Scott


From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jason Fischl
Sent: Sunday, February 19, 2006 2:18 PM
To: resiprocate
Subject: [reSIProcate] Re: [reSIProcate-commit] COMMIT: resiprocate 5978sgodin: - fixed nasty cut-and-paste bug in AclStore - db forAcl's now working

These sorts of accessors are not thread safe if accessed outside of the transaction layer. In general, the transport layer cannot be directly accessed outside of the Transaction layer.

Jason


On 2/17/06, svn@xxxxxxxxxxxxxx <svn@xxxxxxxxxxxxxx> wrote:
Project resiprocate
New Revision 5978
Committer sgodin (Scott Godin)
Date 2006-02-17 14:42:43 -0800 (Fri, 17 Feb 2006)

Log

 - fixed nasty cut-and-paste bug in AclStore - db for Acl's now working
- changed AclStore peer name matching to non-case sensitive
- added some const accessors


Modified:


_______________________________________________
resiprocate-commit mailing list
resiprocate-commit@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-commit