[Gpephone-devel] FW: Proposal of new phoneserver architecture

[Florian Boor]

Hi,

I just noticed I forgot to comment on this :)

JIANG Dan RD-ILAB-PEK schrieb:

>       1)      Phone server manager
> 
> Main program which monitors the IO channel, load and manage plugins, AT
> builder & parser.
> 
>       2)      Plugins
> 
> One plugin corresponds to one service module, such as VOC module, SMS
> module, phonebook module. The service modules are independent from each
> other. Phoneserver loads the modules at initialization.

A status module to generate the DBus signal for the GSM status display would rock.

>             ·       Be easy for expansibility
>             ·       Be easy for add/move modules. E.g., MMS could be
>             easily added to phoneserver as a plugin without recompilation.
>             ·       Make phoneserve manager clean and simple. The
>             current phoneserver is large and complex. It needs support
>             of libmsgenabler, libabenabler. If libmsgenabler or
>             libabenabler is modified, the whole phoneserver has to be
>             recompiled. In the new version, only plugins has to be
>             recompiled. 

Let's say this is a nice feature, but as we usually have all the sources and all
the plugins in one place the benefit of independent modules is quite limited.
If it is easy to achieve its ok, but I would suppose a clean modular code that
supports modules/feature selection at build time would be fine as well.

>       5.      Difficulties
>       How to define a set of interfaces in AT builder & parser module which
> 
>                               ·       Easy for use
>                               ·       Easy for different manufactures to
>                               modify when modem type changes
>                               ·       Fulfill as many functions as possible

This indeed might be tricky, is there someone around who is able to comment on
the differences between some different modems? e.g. if the difference is usually
limited to some initialisation code it would be quite easy, but I guess the
situation is more complicated. Some way to handle non-standard data from the
modem might be to pass this to a callback (or better: to have a signal for that)
in the device-specific module. But we need to be able to add new features anyway
because non-standard AT commands or data are quite likely to be related to some
non-standard feature we might not yet support in the phoneserver.


Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor at kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76