Re: [Easyb2k-devel] Application Structure

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

2007/10/31, Thomas Reitmayr <tre...@ya...>:
> The glue software for sure is specific to the VoIP application which provides its own interface. We _should_ implement the proper glue software for the most common applications, but there should be the possibility for new or not so well-known VoIP apps to access our application. Even if such a VoIP application would implement our D-BUS interface, the strategy of probing all _supported_ VoIP apps fails here as every VoIP application would use a different unique D-BUS object path.
> It should be the responsibility of the glue software _or_ the VoIP app (supporting our D-BUS interface) to probe the daemon, and in the usual scenario that would be the natural order of things, i.e.
> 1. Daemon core is started at boot time.
> 2. VoIP application starts (by user or at boot time) and probes the the daemon core.

2 Will not work with Skype.

The main intention of keeping the glue software inside our daemon as a
plugin is to keep it _flexible_ enough to support *every* weird
protocol that commercial VoIP software may implement.
A separate glue software is _unnecessary_, as the VoIP software may
implement our protocol directly.

the standard use case would be..

Most VoIP applications (active)
         |
         v
---------------------------
|  Standard Glue   |
|           ^              |
|           |    (libdl)   |  Our Daemon
|           v              |
|    Core Daemon   |
----------------------------


And for Skype..

     Skype (passive)
         ^
         |
---------------------------
|    Special Glue    |
|           ^              |
|           |    (libdl)   |  Our Daemon
|           v              |
|    Core Daemon   |
----------------------------


-- 
Daniel Ribeiro