[Gpephone-devel] How to make phoneserver adapt to differenttypesof modem?

[YE NAN RD-ILAB-PEK]

Hi,
In my opinion, we should provide as many approaches as possible to developer which would help them to adapt our phoneserver to thier own modems. I think we could use both configuration files and shared libraries(modules) in future improvement of phoneserver implementation. 
 
The advantage of configuration files is that developers can apply the modification as soon as possible without re-compiling the phoneserver from source code, while the disadvantage is only that complicated parsing workload would increase latency at start-up stage. Due to this, we could put some simple and basic but important parameters in configuration files, such as 
    SERIAL_PORT: {/dev/ttyS0}
    SERIAL_BAUDRATE: {...}
    ATCOMMAND_BUFFER_SIZE:{...}
All these parameter in configuration files have two characteristics:
    1) can be parsed easily, which would rarely affect the perforamance;
    2) deffering much from one modem to another
 
The advantage of share library allows as much as possible freedom for custom functions and we really need it to support different types of modem. But these can be treated as a expert optional porting steps which need developers have certain knowledge with phoneserver structures and our developement environemnt.
 
Best regards,
Nan YE
 
________________________________

From: gpephone-devel-bounces at linuxtogo.org [mailto:gpephone-devel-bounces at linuxtogo.org] On Behalf Of 轶彭
Sent: 2007年3月20日 16:07
To: gpephone-devel at linuxtogo.org
Subject: Re: [Gpephone-devel] How to make phoneserver adapt to differenttypesof modem?



Compared to the configure file solution, I think this one is more reasonable. 

I would like to look into the details of this topic in the following days.

Peng Yi





Dirk Sigurdson schrieb:

> Another option would be to define a shared library interface and to have the
> phoneserver load the correct library based on configuration.

I like the idea as well, but as we usually have a fixed modem setup (the

phoneserver usually needs to support one modem at a time) it should be
sufficient to make this a build time option. But that means that we still need a
decent API for these "drivers" that allows as much as possible freedom for

custom functions in order to support uncommon modems and to make use of common
components (like the GSM command parsing, and ) at the same time.
Of course if it turns out to be necessary we can easily make a shared library

interface from this API.
If someone has an ideas or just wants to collect the requirements we could use
the Wiki for this purpose.

http://www.linuxtogo.org/gowiki/GpePhoneEdition


Greetings

Florian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxtogo.org/pipermail/gpephone-devel/attachments/20070320/49d268f4/attachment.htm