> Had a quick look, and we need to modify the REALM we return an fr_socket_limit_t in the home_server_t based on the key lifetime sent by the trust router.
> Shouldn't be a massive amount of work, thanks for spotting it.
Ok, that's the lifetime of the socket, yes? Can you just help me understand how this changes things?
Let's take an example. You have a fresh request, you get the key lifetime (in this example, 11 minutes) back from the TR, so let's call that time zero elapsed. So you set lifetime in fr_socket_t to 660 (11m * 60), yes? However, you don't want to have the socket hanging around for the entire time (and because you're nice), you set an idle_timeout of what... 30 sec (the default I think). For the next 4 minutes, stuff happens. So that's 240 seconds elapsed. After 30 seconds of idle, the socket closes. That's 270 sec elapsed.
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?
Regards
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.
|