search

camaraproject / DeviceStatus

Repository to describe, develop, document and test the Device Status API family
Apache License 2.0
11 stars 33 forks source link

Semantics of the absence of 'maxAge' #137

Closed javier-carrocalabor closed 5 months ago

javier-carrocalabor commented 5 months ago

Problem description Regarding the usage of 'maxAge' parameter, we have use cases where "real-time" location is needed instead of an x-secs old location. Since 'maxAge' has a minimum value of 60 secs, using 'maxAge' is not a good way for a client to ask for such "real time" location verification. Our proposal is that not including the 'maxAge' parameter in the request (as it is optional) means that the client is requesting a verification of the "real time" location. I saw the same type of proposal in this issue, but there were no more explicit mentions to it in the maxAge issue. So, ¿is this the original meaning of not including 'maxAge' in the request?. For us it is very important to be able to meet this kind of real-time requirement and, doing in this way, both requirements (real-time without 'maxAge' and lastKnownLocation using 'maxAge') could be met.

Expected action Alignment in the semantics of the spec definition.

javier-carrocalabor commented 5 months ago

Wrong repository. I got mixed up. Sorry!