Re: [Easyb2k-devel] Application Structure
Status: Pre-Alpha
Brought to you by:
wyrm
|
From: Daniel R. <dr...@gm...> - 2007-10-31 02:48:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcos wrote: > Now how are going to manage multiple devices and glues without a configuration file ? There is no reliable way to manage multiple (and equal hardware) devices without manual configuration. > I can not see any simpler design than: > 1) The user plugs a device. > 2) The daemon is automatically launched. 3a) If there is just one device, the default configuration tries to load every supported glue, the glue pings the VoIP app only at the probe() function, if it fails the core daemon unloads the unnecessary glue plugin. This will work with *one* device and *N* VoIP applications. 3b) If there are multiple devices, the core daemon looks for the specific device configuration, if it fails to find, the core daemon exit(). If it finds a suitable configuration, it loads the glues according to what the user configured. > To make things simple for the user, a configuration program could be implemented and pop up > whenever the second device gets plugged. We could have two special devices called "GLUE DISABLE" > and "ANY DEVICE". Any newly installed glue will be by default connected to the "any device" > device. A configuration GUI could be implemented, to allow generic configuration, the default configuration will handle most use-cases but some people (even with just one device) will eventually want to "fine-tune" something. ;) > I still have not seen/understood anything simpler.... Daniel, your suggestion does not handle > multiple glues per device. One core Daemon can load N glue plugins. Each device connect event triggers HAL, which loads one instance of the core daemon. In the end it supports N devices, connected to X glue plugins, through N instances of the daemon, and, of course, X has to be greater than N. - -- Daniel Ribeiro -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHJ/tmw3OYl0G0liQRAvpxAKCJ5I9DKU1abvGhSSAPf1JEzPBE9ACgj1oT SAEawNlu66ahlOBp02iq8YY= =diBw -----END PGP SIGNATURE----- |