>
> 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.
|