On Tue, Feb 24, 2009 at 12:02:57PM +0100, Dave Neary wrote: [config-snippet per provider] > Without having thought this through completely, part of the XML format > used by Wengo's SSO seems satisfactory:
Hmm, for advanced things this wouldn't seem sufficient. I'm thinking specifically of server-based presence vs. p2p presence. But there may be other "advanced" settings that need tweaking for specific providers. That said, I like Vadims proposal to make this downloadable, and provide the download-script that parses provider-specific config information (maybe for some other sip client) and computes the qutecom settings from that. (if I've understood vadims proposal correctly). So if the provisioning of a provider changes, there is a certain chance that the provisioning script still works, while a static config needs updating (and a certain number of configs would always be outdated). Of course if the provisioning info changes too much, the config-script would still need changes... My ideas (see last mail on the subject) extend this: Maybe we also want to be able to do customisation of the client (change of pictures, fonts, etc) via scripting. Concerning the language for all this: In the coip branch there are already python-bindings for qutecom if I remember correctly, wouldn't it be nicer to do this in python than javascript? Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting Fax: +43/2243/26465-23 Reichergasse 131 www: http://www.runtux.com A-3411 Weidling email: [email protected] osAlliance member email: [email protected] _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
