Re: [Easyb2k-devel] Application Structure

[Daniel R. <dr...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcos Diez wrote:
> How does the HAL work ?
	I never wrote an application using HAL, I will learn it during the
initial development phase of our project :)
	http://www.ometer.com/hardware.html can give you some pointers on the
motivation behind HAL.

> If I already have two daemon running, with different configuration files 
> each, but no device plugged and the first device gets plugged, will the 
> HAL notice that the daemon is already loaded ? Or will it load a third 
> daemon ? Even if no device gets loaded, how do we know the right daemon 
> will talk to the device ?
	You will *not* have a daemon running *before* the device is plugged.
And if you unplug the device, the daemon should exit. You dont need to
know in advance which daemon will talk to the device, the daemon will
select which .conf file (or .conf section) to use, based on the device's
serial number.

	My idea is just fine when all that matters is the _control_ interface
of the boxes, but we havent discussed how we will configure the VoIP
applications to talk to the right sound device. As the sound codec chip
on the telbox devices are handled by alsa in kernelspace this may be
trouble for future development.
	ATM we can assure that the control interface will match the respective
configuration based on the box serial number, but i dont know how to
assure that each VoIP application will open the correct PCM devices
matching the control interface on the same box.

- --
Daniel Ribeiro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHKBd5w3OYl0G0liQRAhHWAKCCnsYuPcauU/xkjn2Di4K6XSFA2gCfa0hp
KSPCDyXBBSwtT+eSSE8nfQQ=
=/Grm
-----END PGP SIGNATURE-----