[JDEV] Two more avatar issues.

[Dave Smith]

Off a suggestions by pgmillard..

Perhaps this would be a better approach:

<presence to='...' ...>
	<x xmlns='jabber:x:browse'>
		<ns>storage:client:avatar</ns>
	</x>
</presence>

That's the minimal info required -- clients could simply browse to the
resource for more info.

Additionally, in keeping with the browsing spec, one could send presence to
the browsable entity and automatically have updates pushed..

Diz


On Fri, Sep 07, 2001 at 10:10:51AM -0700, Jens Alfke wrote:
>  On Thursday, September 6, 2001, at 04:31 PM, David Waite wrote: 
> 
> 
> > On a different note,  what is the benefit of being able to define 
> > an avatar for different resources? It seems like what a user wants 
> > is to see the same picture for the same person everytime. 
> > 
>  
> Just thought of another, more technical, reason for per-resource 
> avatars. 
> 
> If the avatar image is _not_ per-resource, then every connected 
> resource needs to know immediately when another resource changes the 
> image. Otherwise the next time it sent a <presence> element it would 
> send out a stale hash for the old image. 
> 
> However, this kind of notification won't happen by default since you 
> don't receive <presence> elements from your own resources (right?). I 
> guess you could make it happen by adding yourself to your own roster, 
> but that seems kind of awkward. And there's still a potential for race 
> conditions if two resources try to simultaneously change the image. 
> 
> It's the same fundamental thing I said in the other email: Avatar push 
> is done as part of presence; presence is per-resource; therefore 
> avatars should be per-resource. 
> 
> ?Jens
>