onvif
Cloud Recording command to dynamically accelerate access to recorded segments
This adds the RequestTemporarySegmentDurationOverride command which allows clients to request that a camera records shorter segments on demand. This allows a client to manage costs by configuring cameras for large segment sizes, but dynamically request shorter segments whenever a end-user needs access to the video that is being recorded right now.
This command is optional, and allows a device to offer a better experience for its cloud recording.
Agree with principle of operation. Please find a shorter name or acronym to keep especially capabilities concise. Below I use ShortSegment but there may be a better term.
Suggest to add an optional element ShortSegment to RecordingConfiguration with elements
- Duration and
- Termination
Suggestion to rename method from Request to Set with clarification that calls overwrite previous requests. This would allow to terminate by setting duration to zero.
Editorial:
The method should be defined in the recording configuration section.
Updated based on Hans & F2F feedback:
- Renamed to OverrideSegmentDuration name
- Added the SegmentDurationOverride readonly section in recording configuration target to show what is currently in effect.
Thanks, OverrideSegmentDuration now compiles nicely with Visual Studio :-)
Question regarding behavior over reboot. When clients use short expiration duration they have to frequently update it and storing in flash is problematic. Can we add a note like duration of expiration is expected to be in the range of seconds or minutes and may not persist after device restart. ?
Question, what behavior is expected when a client changes the recording configuration and an override is active? For the sake of simplicity I would prefer that this deletes any previous override.
Updated the element name without Request. SOAP conventions are pretty unclear to the uninitiated!
I agree with both statements regarding reboots & configuration upgrade. I've added a mention to those in the spec. I did not add the range part though, as we already added following the F2F that "The override duration shall not exceed 1 hour." in the spec. This seems like a similar, but stronger requirement so I kept that one.
Already approved. Re-Reviewed updates and I am happy. Good catch by @HansBusch and you have already fixed it by the time I had re-reviewed.