Service Properties's Dialog should have a checkbox to launch (or not) the service on connection

[Fab]

When you setup a service, or right-clic on an existing service to edit his properties (username and password), a checkbox should be here to choose if you want (or not) to connect to this service on this account's connection.

[nk]

you mean be able to not autologin in a transport? Ok I can imagine not sending the presence but maybe it's the transport work to support such feature? At least that is the logic of transports: "act as a normal contact"

[Fab]

you mean be able to not autologin in a transport?

Yes :)

At least that is the logic of transports: "act as a normal contact"

Yes, but in this case, why propose to disconnect on a right clic on a transport ? It make no sense...

When I'm login to my Jabber account, most of the time I don't want to connect to MSN network, but on another side, I don't want to delete this transport, otherwise I'm obliged to reconfigure it each time I need it.

In any case, thank you for time that you pass to make evolve this great software :)

[nk]

yes ok. disconnect on demand is something else. You ask to not autoconnect anyways I'll contact James (the PyMSNt dev) to ask his advice on this (us or he has to support such configurations [it's more logic that he does that so it's client-agnostic])

[asterix]

it's simply impossible. A transport is like a contact, and xmpp doesn't allow us (or maybe with privacy rules) not to send a transport our presence. the server does that, we don't do anything special to tonnect to a transport

[delx]

Hi, James here.

Sorry, this isn't really as easy as it sounds. What the checkbox you suggest would do would make the transport ignore online presence from your account. But then how would it know to log in? The transport can't tell the difference between you actually signing in, and right-clicking the transport and choosing log in.

The best we could do would be to have an option to temporarily disable your account.

You could also use XMPP privacy lists to tell the server to withhold (or not) presence from the transport. That would be the best thing to do.

The only other option would be for me to differentiate between you removing the transport from your roster (presence unsubscribe), and forcing an unregister (<iq type='set'><query xmlns='jabber:iq:register'><unregister/>....) I don't want to do that, because I think we'd end up with a lot of people accidentally registered to the transport, leaving their details lying around on many servers without realising it. Most clients don't actually provide an option to explicitly unregister.

[asterix]

latest solution is ugly. The only one is to use privacy list, and this won't be for 0.9

[anonymous]

World of Warcraft gold( wow gold)--buy

cheap,sell  wow gold.welcome to buy cheap --cheap, easy, purchasing.World of Warcraft,Super fastdelivery of gold, items,and accounts

 膜结构

[asterix]

privacy lists are in now