Messages without type attribute are displayed twice (broadcasts)


Spark shows twice a message without the type attribute.
Notice the type attribute is a recommendation but not a MUST.
It was reported in

How to reproduce:
1- Go to Ad-Hoc message and send
<message to="" type="chat" from=""><body>test123</body><subject/></message>
2- Notice that user1 receives a broadcast and message.




November 13, 2009, 11:07 PM

Apparently this was fixed in the latest releases. Can't reproduce this now. Spark receives just one test123 message via that ad-hoc message.

Daniel Henninger
December 27, 2007, 5:27 AM

Francisco, I can not duplicate this particular issue via the steps you mention here to reproduce. Are you still seeing this?
September 27, 2007, 9:08 PM

Actually, on closer inspection, the raw packets received do indeed have a type='normal' attribute, it's just not shown in the all packets debug display. This is probably not a related bug. No idea why invites are being received as broadcasts as well as invites.
September 27, 2007, 8:19 PM

It looks like invitations to join a conference room, even those initiated by another Spark instance, are among the type-less messages affected by this bug.

Further, if the broadcast duplicate is still open when you click "Accept" on the proper invitation in your chat window, clicking "Accept" has no effect. You have to close the broadcast before clicking "Accept" to join the room. I think that should probably be a separate bug, but I'm not sure, as resolving the duplicates will fix that issue too.

Your pinned fields
Click on the next to a field label to start pinning.




Andrew Seymour


Francisco Vives