<br><br><div class="gmail_quote">On Thu, Jan 13, 2011 at 2:27 PM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">Russell Bryant wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Thu, 2011-01-13 at 16:47 +0100, Klaus Darilion wrote:<br>
</blockquote>
><br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
At least with AIS, we get notified when a node joins or leaves. We<br>
could use that as a trigger to clear all cache entries for a given<br>
server, but we do not do that right now. I don't know the best way to<br>
</blockquote>
<br></div>
This sounds like a good idea.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
deal with it for other distribution methods.<br>
</blockquote>
<br></div>
Maybe XMPP's PubSub supports an expiry as SIP does?<br></blockquote><div> </div></div>Indeed, PubSub (as of the latest version of the spec, anyway) supports an item_expire element. I'll look into adding that to the XMPP devicestate implementation.<br>
<br>Regards,<br>- Brad<br>