I use BOSH to connect join a MUC and at some version i've noticed that last N posts in MUC started to appear in recent-first order thus breaking the continuity:
10:24:42 a> me too
10:24:40 b> fine, and you?
10:23:35 a> how are you?
10:25:25 c> hello guys!
10:25:30 a> hi!
Client is written in StropheJS and just posts message stanzas as they come. Other clients displaying this correctly, maybe they do some sorting inside, but that's pretty compicated and just wrong to do (as that was working before).
Maybe there's a setting to select history order?
I've tried with ejabberd
I've tried with ejabberd 2.1.7/2.1.8, Tkabber TCP connection, Gajim BOSH connection, a MUC new room.
I send messages like "1", "2", "3". Then I open the XML Raw Window of each client, and reconnect to the room. Both clients get the XML messages in the correct order, and they display them correctly.
Check the TCP/XML/XMPP traffic: does your custom-developed client really receive always all the room history in reverse order?
It is. Here's a complete dump
It is. Here's a complete dump of a BOSH response received while joining the conference:
Notice the delay stamps:
stamp="2011-06-06T11:03:32Z"
stamp="2011-06-06T11:03:23Z"
stamp="2011-06-06T11:02:43Z"
stamp="2011-06-06T11:02:30Z"
dp_wiz wrote: that was
that was working before
In what ejabberd version do you remember that MUC history over BOSH worked correctly for you?
What ejabberd version do you have installed now that sends history reversed?
Try with Psi, Jabbim, Tkabber, or other TCP client, do you receive history reversed?
Try with Gajim, configure it to use BOSH, do you receive history reversed?
Show your mod_muc configuration here.
I've been running on 2.1.6
I've been running on 2.1.6 and now installed 2.1.8 from downloads (which strangely identifies itself as 2.1.7 «running on that node») and everything now is in correct order.
Config were pretty generic:
{mod_muc, [%%{host, "conference.@HOST@"},
{access, muc},
{access_create, muc_create},
{access_persistent, muc_create},
{access_admin, muc_admin}
]},
dp_wiz wrote: I've been
I've been running on 2.1.6 and now installed 2.1.8 from downloads (which strangely identifies itself as 2.1.7 «running on that node») and everything now is in correct order.
Ah, now I noticed this ticket:
Regarding the "2.1.7" misleading text: right, that's a mistake in the code. Don't worry.
i can reproduce it in
i can reproduce it in ejabberd 2.1.6