Hi Denis,
> One of the biggest principles in oFono is not to perform premature
> optimization. Sure there is a potential issue, but nobody
> knows whether
> it will actually manifest itself outside of malicious code (which we
> tell to bugger off) or what the most common manifestation
> pattern will be.
>
> If / once we know for sure this is a problem, then we can solve it
> properly. So far this approach has been working very nicely for us.
> There are countless occasions where taking the wait-and-see
> approach and
> gathering more information allowed us to devise a much better solution
> than we would have originally.
>
> So the general rule is: Do the simplest thing that is likely to work.
> If it doesn't work, improve it.
Can't fault the approach, it's generally a good one. That said, I see this more
as an API quality issue rather than an optimization issue. Anyway, I've raised
the concern. Let's hope my worries are unfounded.
Br,
MikaL
_______________________________________________
ofono mailing list
[email protected]
http://lists.ofono.org/listinfo/ofono
