Is an agent the same thing as an infractructure service?
As in the access control white paper:
Delegation allows an account to perform operations with another address as
the
author. Google Wave currently uses this for two cases:
- An account that is a write-member of a group can perform an
AddParticipant
operation to add an address belonging to that account to a wavelet.
- Google
Wave's spelling ("Spelly"), linking ("Linky"), and other infrastructure
services act on behalf of any address in a wavelet with those services
enabled.
...
This provides Google Wave infrastructure services full access to act as a
user, while being authenticated as a service account.
And, if so, is the plan to allow developers to write their own
infrastructure services/agents ?
On Wed, Oct 7, 2009 at 12:36 AM, Brian May
<[email protected]>wrote:
>
> On Tue, Oct 06, 2009 at 09:59:38AM -0400, Joe Gregorio wrote:
> > Slide 17 of this presentation shows the relationship between agents and
> > robots:
> >
> > http://docs.google.com/present/view?id=dggjrx3s_110fkt37dgb
>
> Thanks for this.
>
> So Spelly and Linky aren't robots, they are agents. As I suspected.
>
> (not secret agents I hope ;-) )
>
> What is the justification for this?
>
> (some people have expressed concern that a robot might not be the best
> place to
> implement a EMail/Wave gateway - so this may be relevant to these
> discussions)
> --
> Brian May <[email protected]>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---
