>> Then 2 minutes (at 390 sec elapsed) later you get another request, so
>> you need to set the socket up again. You don't set the lifetime back
>> to 660, right? You set it to (660 - 390) = 270 sec, because the key
>> will expire then?
>>
>> Or is this countdown handled somewhere?
>
> The expiration time in TID_SRVR_BLK is an absolute time, so I think that
> should naturally be compatible with this.
I hope so, because yes, I am aware of the absolute time (hence the question).
:-)
Stefan Paetow
Moonshot Industry & Research Liaison Coordinator
t: +44 (0)1235 822 125
gpg: 0x3FCE5142
xmpp: [log in to unmask]
skype: stefan.paetow.janet
jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
|