RFC: FSO, filtering signals, and interapplication interfaces
Michael 'Mickey' Lauer
mickey at vanille-media.de
Sun Jan 11 16:00:03 CET 2009
First off, thanks for this proposal.
Unfortunately I'm not sure whether this idea is suitable for FSO. I'm not
feeling too well when thinking about the possible consequences.
Assuming your primary use case is a call and SMS firewall, I don't think we
want that in ogsmd. Ogsmd offers simple procedural access to the gsm low
level functions and as such its signals should not be filtered or altered in
any way -- otherwise you change application behaviour for any listeners, such
as call loggers etc.
Going one layer above, it might be more suitable for ophoned, which is the
object-oriented technology-independent voice call service. Then again, I
think I would rather change its API to an agent-model than filter signals.
That way you would get roughly the same effect.
In general though, I question whether these features might be better off
living in the application layer. Remember that a full fledged telephony
application will probably not use the oeventsd rules anyways.
More information about the smartphones-standards