On 26/06/2006, at 8:56 PM, Stian B. Barmen wrote: > man, 26,.06.2006 kl. 20.49 +1000, skrev James Bunton: >> On 15/06/2006, at 6:49 PM, Stian B. Barmen wrote: >> >>> I have this issue with the MSN and ICQ transports. When I am logged >>> on with more then one resource and one of them goes idle the >>> transport goes away. >>> >>> Is this a known issue? >>> >>> Best regards >>> Stian B. Barmen >> >> The transport will set your MSN status to whatever the highest >> priority resource is. >> If you have two resources, one with priority 5, which is online, and >> one with priority 10 - away, your status will be set to away. >> > > Both transports have the same priority, but different resource names. > Seems the one (darkstar) always is above the other (gajim_kontoret) in > pri. If one of these two goes away and the other is online then the > transport should be available in my humble opinion. > > -stian
I've thought about this a great deal, and decided that the transport shouldn't make arbitrary routing decisions. I'm also thinking of where the messages get delivered to. It would make things less predictable. A better idea would be for client developers to make more sensible use of priorities. That is, if you set your client to available, it should make sure it has the highest priority. If it goes idle, set the priority lower. I believe some clients already do this. --- James
