<p dir="ltr"><br>
On 26 Mar 2014 20:59, "Waqas Hussain" <<a href="mailto:waqas20@gmail.com">waqas20@gmail.com</a>> wrote:<br>
><br>
> On Wed, Mar 26, 2014 at 2:05 PM, Dave Cridland <<a href="mailto:dave@cridland.net">dave@cridland.net</a>> wrote:<br>
> ><br>
> > On 26 Mar 2014 17:49, "Daniel Dormont" <<a href="mailto:dan@greywallsoftware.com">dan@greywallsoftware.com</a>> wrote:<br>
> >> I have a use case where I would like to send a presence to a MUC that<br>
> >> I may have already joined and, even if I have, I want it to send me<br>
> >> the message history no matter what. Is there a way to do that or would<br>
> >> it require a protocol extension of some sort?<br>
> ><br>
> > Yes and no.<br>
> ><br>
> > Technically speaking, simply sending presence to a MUC and joining (thus<br>
> > getting the history and participants) are not the same thing. Sending a<br>
> > proper MUC join (with the <x/> and the history control optionally inside it)<br>
> > to M-Link[*] will, therefore, give you the history you asked for, and all<br>
> > the occupant presence, even if you're already in the room.<br>
> ><br>
> > I find this *extremely* useful - which is why I did things that way. A<br>
> > use-case for this is where an S2S link is down when you reconnect your C2S,<br>
> > or the server crashes, or ... - all arguably edge cases, but they're solved<br>
> > very nicely this way.<br>
> ><br>
> > Other servers don't do this, though - I think they should.<br>
> ><br>
> > If you wanted to avoid the occupant presence, you'd want an extension which<br>
> > signalled this in much the same way that the history controls work.<br>
> ><br>
> > Dave.<br>
> > --<br>
> > * - Note that I left Isode over a year ago and so may well be out of date.<br>
> ><br>
><br>
> Prosody was (AFAIK) the first server to do this. We specifically<br>
> checked for <x xmlns=muc>, and assumed it was a MUC join, even if the<br>
> user was already in the room. It worked wonderfully, but we had to<br>
> comment that out because of Gtalk resending directed presence every<br>
> few minutes.<br>
></p>
<p dir="ltr">Yeah, I decided at the time correct behaviour over flakey links was more important than supporting buggy servers.</p>
<p dir="ltr">I suppose it could have been made an option, in retrospect, but I did really appreciate the support on internet servers too.</p>
<p dir="ltr">> Did Google ever fix that? Or do Gtalk users joining M-Link chatrooms<br>
> get history sent over and over? We never removed the code from Prosody<br>
> in the hope that Google would fix their behavior and we would reenable<br>
> the feature.<br>
></p>
<p dir="ltr">I've no idea. I know it was quite irritating for a while use a Google account with an M-Link chatroom.</p>
<p dir="ltr">> --<br>
> Waqas Hussain<br>
> _______________________________________________<br>
> JDev mailing list<br>
> Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a><br>
> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br>
> _______________________________________________<br>
</p>