Hi Rob, I'm using telepathy-mission-control and telepathy-gabble. I spent some time on source code and walked throuth related parts and now understands most of them well.
telepathy-gabble really requires a https proxy setting rather than normal http proxy. So my enviornment doesn't meet it. But it might be deserved to add non-secure http proxy support. That should be easy if it can support http proxy setting. telepathy-mission-control reads both profile file and manager file. There are three types of storages for parameters, Gconf, Profile file and Manager file. Gconf is manipulated with mc_account_set_param_XX(). mc_account_get_param_xx() can returen all three types storage with priority up from Gconf, ProfileDefault then to ManagerDefault and system proxy(for http-proxy-xx, https-proxy-xx). Note, while http-proxy-xx is supported by MC, it's NOT supported by gabble. To make a connection to gabble, it reads parameter by mc_account_get_params() only from Profile and Manager file, missing Gconf. Here it seems to be a MC bug since MC supports read of system proxy. Thanks, Peter Robert McQueen wrote: > Zhu, Peter J wrote: >> Hi Rob, > > Hi Peter, > >> Thanks for quick response. Then comes three more questions: >> (1) Which component reads the manager file? > > Mission control and/or a UI which is responsible for managing the > accounts, launching the connection managers and creating the > connections. > >> (2) According to your statement, if I understands correctly, in any >> case the default value will be fed to connection manager in process >> of RequestConnection, but it just can't get gabble work > > No, the .manager file isn't used as a source of the default settings, > the .manager file just tells people what the defaults are. It can be > viewed as a cache of the information that you can get from > ListProtocols and GetParameters on the ConnectionManager interface, > but allows that to be accessed by clients without launching every > manager installed on the system. > >> (3)Strangely why there is a extra 's' in the pair of parameters, why >> not just name of http-proxy-server/http-proxy-port? > > All that Loudmouth supports is making an HTTP CONNECT request, which > is used for establishing HTTPS connections through proxies, so we > call a proxy that supports CONNECT an HTTPS proxy. > _______________________________________________ Telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
