#76: QuteCom sends too much PUBLISH
---------------------+------------------------------------------------------
Reporter: ibc | Owner: vadim
Type: defect | Status: new
Priority: major | Milestone: QuteCom 2.2-RC4
Component: phapi | Version: 2.2-RC3
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by laurent):
Replying to [comment:24 ibc]:
> - When any other client, '''including Qutecom''', receives the second
PUBLISH it will display the user as "online" as the <basic> field says
"online". If at least Qutecom would keep the <basic> element instead of
setting it to "open"... but well, all this stuff is really wrong :(
Replying to [comment:24 ibc]:
> - When any other client, '''including Qutecom''', receives the second
PUBLISH it will display the user as "online" as the <basic> field says
"online". If at least Qutecom would keep the <basic> element instead of
setting it to "open"... but well, all this stuff is really wrong :(
You're mixing 2 things :
It is not because basic == online that QuteCom show contact as Online when
it receive a mood, at this level it fix presence at
EnumPresenceState::PresenceStateUserDefined
see
[http://trac.qutecom.org/browser/libs/sipwrapper/src/phapi/PhApiCallbacks.cpp]
PhApiCallbacks::onNotify
At an upper level, ContactManager detect an activity, so it put the
presence to online ...
see
[http://trac.qutecom.org/browser/wengophone/src/model/contactlist/ContactList.cpp]
ContactList::presenceStateChangedEventHandler
--
Ticket URL: <http://trac.qutecom.org/ticket/76#comment:26>
QuteCom <http://trac.qutecom.org>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
