Closed bsriramprasad closed 5 months ago
20240312 Video Enhancement F2F
Further discussion on point 2
Here are 2 Possible interpretations of the requirement text for non-native English speaker
The device should attempt to create connections to all entries in the uplink list at the same time, without waiting for one connection to be established before trying the next.
The device should try to establish connections to each entry in the uplink list one after another, but if there are multiple connections that can be established simultaneously (such as connections to different servers), it should do so.
I understand the use case that device to keep connection simultaneously to say vendor cloud and 3rd party cloud. But that doesn't mean the device needs to set up or initiate those connections exactly at the same time?
If a device is a bit short on resources, It may set those connections one by one and that should not disqualify the device in adhering to the uplink specification.
Ideally, it shouldn't matter how and when the device gets connected to multiple clouds as long as it can keep those parallel connections alive - which keeps up the spirit of the specification.
Proposal
device connecting to multiple clouds one bye one or or simultaneously is device implementation specific behavior, ONVIF interface(i.e Uplink spec here) should not mandate it.
The connection to all in parallel has been defined by purpose for allowing multiple cloud services using the same camera. We had a discussion on alternates but dropped that because such things can be solved differently.
@HansBusch Its not about having connections to multiple cloud services - but It is about ONVIF specifying how those connections are made to those services "shall try to establish all connections in parallel."
Here is the updated proposal
Got your point and agree.
3) [Specification Text] Since http/2 streams may be closed by either side when the content-length has been reached clients shall use a value large enough for the connection life time.