TelescopeStatus model says nothing about the maximum update rate it expects

[pothiers]

I get pointing information for one of our telescopes that indicates where it is pointing in real time. That can change many times per second. If we use the API to update pointing information, it may look a lot like a Denial Of Service attack!

Perhaps the model should specify the maximum update rate or the minimum distance in pointing angle to be consider to be a new pointing location,

[jnation3406]

I think the intention of recording telescope pointings is more for a record of what targets were observed rather than a record of raw telescope pointing telemetry. I assume when you say its changing in real time many times a second this is more a telemetry stream as the telescope is slewing rather than the final position its pointing while exposing, is that correct?

[pothiers]

That might be true. But as it stands the data I can get doesn't make the distinction. And if it did, for some telescopes the current exposure pointing data cannot be released to the public until after some quarantine period.
The endpoint is "telescope-statuses" which is more general than "exposure info". If the point is to support MMA, then knowing where the telescope is pointing especially when it is not exposing would seem to be important.