<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>No, you do get presence from your other
resources.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Julian</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jens@mooseyard.com href="mailto:jens@mooseyard.com">Jens Alfke</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=jdev@jabber.org
href="mailto:jdev@jabber.org">jdev@jabber.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, 07 September, 2001
13:10</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [JDEV] Two more avatar
issues.</DIV>
<DIV><BR></DIV>On Thursday, September 6, 2001, at 04:31 PM, David Waite
wrote:<BR><BR>
<BLOCKQUOTE>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.<BR></BLOCKQUOTE><BR>Just
thought of another, more technical, reason for per-resource avatars.<BR><BR>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.<BR><BR>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.<BR><BR>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.<BR><BR><?fontfamily><?param Marker Felt><?color><?param 0000,5151,0101><?bigger><?bigger><?bigger>—Jens<?/bigger><?/bigger><?/bigger><?/color><?/fontfamily></BLOCKQUOTE></BODY></HTML>