Re: [ogpx] Seed capability behavior

[Hogmanay Milestone <[e-mail]>]

----- Original Message ----
From: Infinity Linden (Meadhbh Hamrick) <[e-mail]>
To: David W Levine <[e-mail]>
Cc: [e-mail]; "[e-mail]" <[e-mail]>
Sent: Wed, January 20, 2010 4:43:58 PM
Subject: Re: [ogpx] Seed capability behavior

>1.1. if the seed cap persists for a fixed period of time, the client
>may request additional services from the seed cap later. it's possible
>we may want to wait to issue service caps until the client actually
>tries to do certain things (like spend money, transfer items,
>inventory access, etc.)

but how likely is this to happen?

>1.2. if the seed cap persists for a fixed period of time, it allows
>service caps to have shorter lifetimes. deployers may want some caps
>(like caps for spending money and transferring items) to have a
>shorter lifetime than others (like caps for connecting to public
>regions or caps for getting the grid status.)
> 
>by persisting the seed cap, the client may request a new service cap
>from the seed without having to re-authenticate.


you could request a "new seed" capability from the seed cap, then when you need a new one, you access the new seed capability to give you a new seed capability.