| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
I
downloaded the latest source code, it still doesn't work. I think I know why: my
application returns 30 on the on the onRequestRetry() callback. The
code for handling delayed retries is in ClientRegistration.cxx, line 503. It
doesn't change the mUserRefresh flag to true, but the immediate
retry case (return code 0) does change it.
Hagai. From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx] Sent: Tuesday, November 14, 2006 3:53 PM To: Hagai Sela (TA); resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: RE: [reSIProcate] Problem with client registrations in DUM This
logic was just recently changed – I can’t remember if it made it into 1.0.1 or
not, but it should work using the SVN head version. From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Hagai
Sela (TA) Hi, I have the following
scenario: a resiprocate based client registers successfully using DUM, with an
expiration period of 30. After 25 seconds it tries to re-register, but the
second request receives 408. After a while a third request is sent, and it
receives 200 OK. My application doesn't receive the onSuccess() callback for the
third request. I looked at the DUM
code. In ClientRegistration.cxx, line 449. There is an if statement that checks
if this 200 response is a user refresh request, and only if it is the
application is notified. The above scenario doesn't fit this logic, the
application should be notified even if this is not a refresh
request. Hagai. |