Re: [reSIProcate] ServerRegistration.cxx lockRecord without corresponding unlockRecord ?

["Justin Matthews" <jmatthewsr@xxxxxxxxx>]

Nevermind.  I get it.  This is done to keep the "transaction" uncommitted
until the current request is rejected or accepted.  If its rejected the
"transaction" is rolled back.

Thanks,

-Justin

-----Original Message-----
From: Justin Matthews [mailto:jmatthewsr@xxxxxxxxx] 
Sent: Thursday, November 02, 2006 10:34 AM
To: 'resiprocate-devel@xxxxxxxxxxxxxxxxxxx'
Subject: ServerRegistration.cxx lockRecord without corresponding
unlockRecord ?

In ServerRegistration.cxx:143, ServerRegistration::dispatch(const
SipMessage& msg), there is a call to database->lockRecord().  There is not
corresponding database->unlockRecord() calls before return'ing from this
function in all cases (lines 162, 197).  Is this intended? 

Thanks,

-Justin