stv0g/spectrum2
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Do not treat transport contact as buddy

Browse source
This commit is contained in:
HanzZ 2012-04-11 17:59:19 +02:00
parent 9d5e0793e0
commit 64a0ece8d3
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
src/rostermanager.cpp
View file

@ -232,7 +232,10 @@ void RosterManager::handleRemoteRosterResponse(boost::shared_ptr<Swift::RosterPa
if (m_buddies.find(legacyName) != m_buddies.end()) {
continue;
}
std::cout << "LEGACYNAME " << legacyName << "\n";
if (legacyName.empty()) {
continue;
}
BuddyInfo buddyInfo;
buddyInfo.id = -1;
@ -240,6 +243,7 @@ void RosterManager::handleRemoteRosterResponse(boost::shared_ptr<Swift::RosterPa
buddyInfo.legacyName = legacyName;
buddyInfo.subscription = "both";
buddyInfo.flags = Buddy::buddFlagsFromJID(item.getJID());
buddyInfo.groups = item.getGroups();
Buddy *buddy = m_component->getFactory()->createBuddy(this, buddyInfo);
setBuddy(buddy);
@ -291,6 +295,10 @@ void RosterManager::sendRIE() {
void RosterManager::handleSubscription(Swift::Presence::ref presence) {
std::string legacyName = Buddy::JIDToLegacyName(presence->getTo());
if (legacyName.empty()) {
return;
}
// For server mode the subscription changes are handler in rosterresponder.cpp
// using roster pushes.
if (m_component->inServerMode()) {