Hi Denis, 2009/9/2 Denis Kenzior <denk...@gmail.com>: > So the general rule is that if a feature isn't explicitly allowed in 27.007, > we do not support it. There are exceptions to this of course. 27.007 only > supports two states for context: activated and deactivated.
Ahem. Just like access selection mode is not in 27.007, yet Nokia has it, and most AT modems have proprietary commands to query and set it [1]. Maybe you call that the necessary exception to the rule, but I think we might as well change the rule to: "If a feature is explicitly requested by users of oFono, and can be reasonably provided by modems that have it without braking those that don't have it, it will be supported. And 27.007 can go fsck itself." ;-) >> spec 27.007. However, the problem is that Maemo 5 already has UI >> support for indicating that the connection is suspended, and that >> makes it harder to drop the feature. Could the "suspended" status enum >> still be left there, and just have the modems that don't support the >> feature to never go to "suspended" mode? > > I'd rather not. > > If this feature is really required, then some sort of heuristic can be > applied. (e.g. Powered on, Attached on, but context is deactivated most > likely means temporary unavailability of resources) You want the UI to implement this heuristic, when the modem plugin has explicit knowledge of that state, but isn't telling? Please explain how that makes the UI simpler? Cheers, Aki [1] http://blogs.gnome.org/dcbw/2009/03/20/thats-when-i-reach-for-my-revolver/ _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
