|
xuanzx xuan opened 8 years ago
|
|
|
Sorry to put the question at the wrong place.But ... how to move it away ... |
|
I tried to verify this issue on Tigase XMPP Server 7.1.0-SNAPSHOT (todays build) and all works fine - messages are delivered. I used latest stable build of strophe-js and stream-management plugin for strophejs from strophejs-plugins GitHub repository. However initially I had an issue that message was not delivered but it was in fact due to my mistake as since Tigase XMPP Server version 7.0.2 it is required that XMPP client sends initial presence before any message sent to it's bare jid will be delivered to him (if not then message will go to offline storage). Do you send initial presence as you connect to server? It is important that this presence must have priority omitted or set to nonnegative value. This requirement is from RFC 6121, Section 8.5.3.2.1. Message |
|
|
Thanks for your rescue! It is a mistake of initial presence as you said.Because of a bug of strophe.stream-management.js, the send was skip with no error report. |
| Type |
Bug
|
| Priority |
Minor
|
| Assignee | |
| RedmineID |
4486
|
| Spent time |
5h
|
I tried to use websocket with stream management.Client A use smack(c2s) and client B use strophe(ws2s).The result is:
B can send message to A, but B can not recieve message from A.
B can receive from tigase server if B send after send a message.
Without stream management enbled, B can communicate narmally with A.
It seems like the message from A did not drop the message to the queue of ws2s.
ps.1:I set ws2s/processors as same as c2s/processors.
ps.2:I remember that I have seem a page in this website, which contains 'to support XEP-0198 for websocket' with timestamp 2013-xx-xx.