5.2.20
12/08/2019

[#184] ChatStateFilter problem
Summary ChatStateFilter problem
Queue gloox
Queue Version SVN
Type Bug
State Unconfirmed
Priority 2. Medium
Owners
Requester euroelessar (at) ya (dot) ru
Created 05/27/2010 (3482 days ago)
Due
Updated 03/13/2015 (1731 days ago)
Assigned
Resolved

History
03/13/2015 10:47:39 AM shmakov (dot) ivan (at) gmail (dot) com Comment #3 Reply to this comment
recieved does not standart tag
http://xmpp.org/extensions/xep-0085.html

to ignore it comment

m_enableChatStates = (state->state() != ChatStateInvalid);
03/13/2015 10:44:54 AM shmakov (dot) ivan (at) gmail (dot) com Comment #2 Reply to this comment
40c40,43
<       m_enableChatStates = state && state->state() != ChatStateInvalid;
---
       if (!state)
           return;

       m_enableChatStates = (state->state() != ChatStateInvalid);
05/27/2010 10:16:31 PM euroelessar (at) ya (dot) ru Comment #1
State ⇒ Unconfirmed
Queue ⇒ gloox
Summary ⇒ ChatStateFilter problem
Type ⇒ Bug
Priority ⇒ 2. Medium
Reply to this comment
If ChatStateFilter recieves smth like:
<message from='foo@qutim.org/qutIM' to='boo@qutim.org/qutIM
xml:lang='ru' id='uid:4bfee8d7:4c569893' type='chat'>
<received xmlns='urn:xmpp:receipts'/>
</message>
it thinks that foo@qutim.org/qutIM doesn't support ChatState's which 
is wrong. This receipt answer was prepared inside of 
MessageFilter::filter method and sended by invoking method 
"MessageSession::send", so message wasn't decorated by other Filter's.
There are two ways for resolving this problem:
1. Doesn't change ChatStateFilter::m_enableChatStates if message has 
empty body
2. Call decorate for messages, sent from MessageFilter
I think first way is more acceptable