Hi,
Vadim Lebedev wrote:
> 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:
...
> Any comments?
This does not need to be tied to provisioning, I think.
I proposed previously the following idea, which would be I think very
useful - a configuration file per SIP provider, detailing all of the SIP
configuration needed to connect (realm, proxy, port, etc) which could be
parsed on demand by QuteCom and which would allow the user to only have
to choose his SIP provider, enter his username and password.
The SIP providers would have a very simple file format in which to
provide server-side configuration, we could build up a database of
user-contributed configs, and we could ship the 10 most popular with the
QuteCom, have the others available in the wiki for user download.
Without having thought this through completely, part of the XML format
used by Wengo's SSO seems satisfactory:
<provider>
<name>Wengo</name>
<realm>voip.wengo.fr</realm>
<proxy>
<host>213.91.9.206</host>
<port>5060</port>
</proxy>
<server>
<host>voip.wengo.fr</host>
<port>5060</port>
</server>
<httptunnel>
<host>httpproxy.wengo.fr</host>
</httptunnel>
</provider>
We would have a directory /usr/share/qutecom/providers, and a either a
user-specific directory ~/.qutecom/providers which contain one XML file
per provider, parsed at the time we need to populate the combo box to
show the log-in screen. The log-in screen would stay the same, and the
"Configure a new provider" screen would change to:
Provider: | \/| (drop down box with providers - "Other" is
the last one)
Username: | |
Password: | |
Display name: | |
(the remaining fields are filled automatically when selecting a provider
and are read-only, unless the provider is "Other").
Since we already have code to parse the Wengo config files, it should be
pretty easy to extend this and re-use it more generally.
What do you think?
Cheers,
Dave.
--
maemo.org docsmaster
Email: [email protected]
Jabber: [email protected]
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
