mwiktowy
|
2008-03-02
, 17:44
|
Posts: 373 |
Thanked: 56 times |
Joined on Dec 2005
@ Ottawa, ON
|
#41
|
|
2008-03-02
, 18:05
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#42
|
|
2008-03-02
, 20:54
|
Posts: 472 |
Thanked: 107 times |
Joined on Apr 2007
@ Texas
|
#43
|
|
2008-04-06
, 15:51
|
Posts: 19 |
Thanked: 9 times |
Joined on Jan 2008
|
#44
|
|
2008-04-07
, 12:23
|
|
Posts: 42 |
Thanked: 6 times |
Joined on Sep 2007
|
#45
|
|
2008-04-07
, 14:04
|
Posts: 19 |
Thanked: 9 times |
Joined on Jan 2008
|
#46
|
|
2008-04-07
, 14:11
|
|
Posts: 1,076 |
Thanked: 176 times |
Joined on Mar 2007
|
#47
|
|
2008-04-07
, 14:16
|
|
Posts: 868 |
Thanked: 474 times |
Joined on Oct 2007
@ Capital District, NY, USA
|
#48
|
I also realised (by looking at the output of dbus-monitor) why opening the contacts list is so slow and uses up 100% cpu. It seems, upon opening, this list queries the online status of every contact in your list against all the im servers. I would've thought that it maintains this list in the background like most im clients. When you have a lot of contacts, this process is slow.
|
2008-04-08
, 10:25
|
Posts: 19 |
Thanked: 9 times |
Joined on Jan 2008
|
#49
|
Is it really querying the servers, or just the dbus calls to the telepathy backend?
There is the persistent IM backend ( telepathy ) that does all the protocol stuff and then the front end ( chat_ui, contact list, ... ) can be closed completely and will query for the state information when it is launched from telepathy ( not necessarily the actual IM servers ).
|
2008-04-08
, 15:02
|
|
Posts: 1,878 |
Thanked: 646 times |
Joined on Sep 2007
@ San Jose, CA
|
#50
|