Hi Claudio, Anderson,
>> Sorry, actually it was a mistake from Claudio (which I hadn't noticed
>> when I made my comments) :) This is a *Monitor* API as I mentioned.
>> The doc itself mentions:
>>
>> +Interface org.bluez.ProximityMonitor
>>
>> And you are correct, our current focus is on Proximity Monitor & Find
>> Me Locator (AKA "client") roles. The "server" roles will be initially
>> implemented for testing purposes.
>>
>
>It will be fixed. Sorry!
Thanks for clarifying.
>Yesterday discussing internally here we found some issues:
>1. SetProperty("FindMeAlertLevel", level): needs a timeout. LE Create
>Connection Command doesn't have a timeout, but the L2CAP socket(~40s)
>and D-Bus message(~20s) have.
>2. SetProperty("FindMeAlertLevel", level): needs a cancel mechanism?
>Maybe setting it to "none" is enough.
>
>LinkLossAlertLevel and PathLossAlertLevel are ok: timeout not
>necessary. The last one is LOCAL and used only when the threshold is
>reached.
How about if there is a connection loss before Monitor could write the Alert Level into Reporter? In this case Monitor would try to reconnect based on Auto connection procedures but won't PathLossAlertLevel need a timeout here ... [wild speculations :-)]
Also how about setting profile specific LSTO? Proximity specs recommends this value to be 6X connection interval but I guess we may give the user/application some flexibility to play around on this? Same may be the case for connection interval, scan interval, latency values etc...I believe these values can be pretty much user/platform specific and user should have control over these ...
Thanks,
Arun
��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
