Re: Ofono CF states not always correct

[Denis Kenzior <denkenz@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi Pekka,

On 01/18/2011 03:32 PM, Pekka Pessi wrote:
> Hi Denis,
> 
> 2011/1/18 Denis Kenzior <denkenz@gmail.com>:
>> I think we can track the cached flag for conditional CFs independently
>> from CFU.  The question is really whether the networks allow us to
>> modify conditional CFs when CFU is active.  In my testing the answer is No.
> 
> You can erase (##67#) or deactivate (#67#) them.
> 

So CFB active.

Activate CFU
Query CFB -> Inactive

Deregister CFB -> OK
Query CFB -> Inactive

Register CFB -> Error

Deactivate CFU
Query CFB -> Inactive

Correct?

Jeez, who thought this stuff up.

So my thinking is that we should:
- Not update conditional cfs when cfu is active (whether via
GetProperties or mmi)
- only clear the conditional cache flag if a conditional operation is
attempted and succeeds while cfu is active
- Report conditional cfs as empty when CFU is active (and emit signals
appropriately when cfu is activated / deactivated)
- Don't bother running conditional cf queries via GetProperties if cfu
is active

Do you see any issues with this?  I'm really trying to minimize the
number of queries we have to do in the most common case (which is
activating / deactivating cfu via settings)

Regards,
-Denis