[reSIProcate] client-side subscription refresh - expires valu e

[Scott Godin]

Hi Elizabeth - this seems like a reasonable thing to want to do.  I just
committed a change to both ClientSubscription and ClientRegistraion to allow
you to specify an optional new expires value.  The default is to use the
original value.

 

Scott

 

  _____  

From: Elizabeth Clark [mailto:elizabeth.clark at bridgewatersystems.com] 
Sent: Friday, March 18, 2005 9:44 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] client-side subscription refresh - expires value

 

Hi,

I noticed the ClientSubscription class does not allow the caller to specify
an expires value when refreshing a subscription. This is the
requestRefresh() method. I believe this is a limitation. As a result, all
refreshes are done using the initial expires value.

 

It looks like the solution is simple - just allow an expires argument and
assign it to the expires header.

 

Regards,

Liz

 

 

Elizabeth Clark                                 
Bridgewater Systems Corporation                
Phone :  (613) 591-9104 x2776
E-mail :  <mailto:elizabeth at bridgewatersystems.com>
mailto:elizabeth at bridgewatersystems.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050324/693055c9/attachment.htm>