Communication from App to Recording servers

Hello,

I would like to know more about the communication flow between the different components in a Milestone XProtect enterprise setup including interfacing with a third-party application using the API.

In our setup we have multiple recording server (let’s say 3) and we have a third-party application that needs a single frame from multiple cameras (let’s say 9).

  • Do the Management Server generate 3 individual tokens to communicate with the 3 recordings servers?
  • Will it generate a delay by not grapping the frames from all the cameras on one recording server before moving on to the next recording server?
  • What is the expiry and refresh policy for the tokens?

I 've tried to illustrate the setup below. A scenario could be that our application requires a frame from each of the 9 cameras. Afterwards the application goes to idle and maybe 4 hours later a new request is send with frames from the same cameras. How would this work?

Thanks in advance!

Br,

Mads

You get one token from the Management Server, and you use that token for all services and all recording servers.

Depending on the implementation there can be very little delay, you can implement contacting recording servers and getting frames to work in parallel.

When you get the token you also get information on when it will expire, by renewing the token before it expires you can implement something that works without interruption.

The TCPVideoViewer sample is using protocol methods, it has the recommended refresh of token. https://doc.developer.milestonesys.com/html/index.html?base=samples/protocolsamples/tcpvideoviewer/readme.html&tree=tree_3.html