maxage not working

Hi Chris,

The ‘maxage’ parameter only works for actual live tracks, i.e. tracks that are requested with the ‘user=’ parameter.

Specifying tracks by ID and adding ‘live=true’ doesn’t make them live tracks in that sense, it merely tells the Javascript to reload the tracks every 10 seconds as if they were live tracks.

I realize that this may be a bit confusing, and right now I can’t think of any compelling reasons why ‘maxage’ shouldn’t apply to all tracks, other than that it doesn’t really make a lot of sense, if you view tracks that are specified by ID as non-updating. It least, that’s how they were intended, and that’s why the concept of live tracks (user=) was invented.

‘Live=true’ is merely a hack, mainly intended to work with external files (GPX/KML).

Best regards,
Martijn.

• This reply was modified 4 years, 3 months ago by tinuzz.

Can you tell me a bit more about your use case, i.e. why are you using ‘track=1,2,3,4,5 live-true’, rather than ‘user=@,a,b,c,d’ ?

In my mind, a single user should have only one track that is considered ‘live’. I know you can have multiple apps running, creating different (but mostly identical) tracks in parallel, but that doesn’t really sound very efficient to me in real life, or at least it doesn’t seem like something you’d want to bother your visitors with.

Cheers,
Martijn.

Ah OK, thx for the clarification .

The moment I read your answer I was asking myself the same question :).

Tried it now with user and it works like I wanted it to work.

Thank you ??

Great!!

Cheers,
Martijn.