Re: [ogpx] Seed capability behavior

ogpx-bounces@ietf.org wrote on 01/20/2010 05:16:54 PM:

> [image removed] 
> 
> [ogpx] Seed capability behavior
> 
> Hurliman, John 
> 
> to:
> 
> ogpx@ietf.org
> 
> 01/20/2010 05:17 PM
> 
> Sent by:
> 
> ogpx-bounces@ietf.org
> 
> The current handling of seed capabilities in Second Life is that 
> they are treated like one time capabilities. The viewer knows a list
> of all of the capabilities it wants ahead of time, and makes a 
> single request containing the full requested capabilities list. Are 
> we mandating that VWRAP seedcaps must be one time capabilities or 
> must not be one time capabilities? If it’s up to each 
> implementation, we’ll get a situation where some clients make 
> multiple requests to a seed cap and are incompatible with services 
> that chose to implement one-time seedcaps.
> 
> John_______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx

My (fairly strong) preference is that they be persistent caps. I see no 
reason to force a client into the model of
asking for (and keeping track of) everything when it doesn't need it. 
Making it possible to pull caps as you need
them is upwards compatible with getting them all at once, and allows a 
more flexible usage.

I'd also point out that, if a service provides a "short term" cap which 
expires, we need a way to permit the client
to renew the cap, so that also strongly argues for a persistent cap, and, 
a fine grained one as well. I would
not want to force a re-get of every cap, when any single cap expired. 

- David 
~ Zha 