+1 Laurent
----- Original Message ----- From: "Ralf Schlatterbeck" <[email protected]> To: "Vadim Lebedev" <[email protected]> Cc: <[email protected]> Sent: Tuesday, February 24, 2009 10:52 AM Subject: Re: Provisioning infrastructure > On Tue, Feb 24, 2009 at 04:15:19AM +0100, Vadim Lebedev wrote: >> Folks, >> >> We're mullingbhre the idea to implement generic provisioning mechanics: >> >> The idea is following: >> >> We'll have a config file with the list of tuples describing >> Provisioning services: >> >> Each tuple will contain a title which will be displayed and a file >> name which wilh hold an html page containing javascript code. >> We'll use Webkit to load the page (without displaying) >> We'll call the javascript method providing it the userid and password >> enterd by the user, the javascript will do whatever it has to do >> (contacting http servers for exemple) >> to retrieve the provisioning info. >> The javascript will return to qutecom an xml doc containing >> provisioning info (server addresses, login, some other stuff TBD) >> >> Qutecom will use this info to register with the sip server. > > Sounds very interesting. > Do I get that right: The javascript would be (contributed) part of > qutecom for a specific service (or maybe a (hopefully trusted) remote > url), so there could be scripts that compute the qutecom config format > from whatever is available from the provider of a specific service. > > What about allowing simple customisations too, not only the config.xml > but also e.g., a set of background pictures and color settings? > > 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 > _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
