We are working on a project for an internal development that uses Milestone MIP SDK in order to manage our Milestone XProtect Corporate system and access video and recordings.
Having said that, we did a lot of progress with our development and now that we are performing deeper testing some questions came out. So here I am asking for help from your side.
Right now, we have an .NET (winforms) application running on Windows 10 x64 machine that uses MIP to connect with our XProtect Corporate system and above other things, brings live video and show it into the screen. Having said that and considering the experience we have with Milestone Smart Client (in this case we are not using SMART client at all), we did some testing and modified token time out to 5 minutes.
Here you have what I modified from ServerConfig.xml file:
5
60
Then, we turned off the management server.
At that moment we expected to lost connectivity to live video after a maximum time of five minutes. Strange thing is that we never lost the streaming, we leave the App working for more than an hour but live video keeps workings fine. We are a little bit lost at this point because it seems that token is not being used by our system (that’s not a problem for us but we would like to make sure if we are missing something or not).
Important to say, our app was based on the following example: Files\Milestone\MIPSDK\ComponentSamples\PlaybackUser
I hope my explanation was clear. I am not a developer myself so I tried to be as much pragmatic as possible.
Could you help me clarifing what should be the expected behavior considering the type of integration we are doing. What happened to us, is this the expected behavior?
Thanks in advance for your help.
Regards.
Hi Bo, thanks a lot for your answer. In our Dev enviroment we are using Milestone XProtect Corporate 2018 and MIP SDK 2018R3. Nonetheless, in our Production enviroment we are still using XProtect Corporate 2016R3 and the objective is to use it with MIP SDK 2018R3 as well.
If I got it right, the difference you mentioned above between the way token timeout is configured depends on Milestone XProtect version and not in which MIP SDK we are using, is this right? can you confirm?
From a general point of view, can the token time out be configured as infinitive so we never lost connectivity?
I modified the file that is mentioned in one of the articles and now it seems the token is being taken into consideration. Anyway, I am not able to “calculate” the time from wich point the connection is rejected.
I did the following:
- Open my application, I start to see live view.
- Turn off management server.
- Access [C:\Program](file:C:/Program) Files\Milestone\XProtect Management Server\IIS\ManagementServer\ and set ClientTokenTimoutMinutes=2 within web.xml file.
- Turn on server management.
- Restart my application.
- Turn off management server.
- At this moment, the behavior is not always the same. In general, if I increse the token, the connection is hold for a longer time but it never reach the number of minutes I set.
Thanks for your help.
Regards.
I confirm there are two different methods: 1) 2017R3 and newer. 1) Older than 2017R3.
You cannot set set infinite, I have no information what the maximum configurable value is.
Please see the note (in both knowledge base articles):
"Please note that if tokentimeout is 60 minutes, the time Smart Client will continue to work is maximum 1 hour.
If you received a token 30 minutes ago when the Management Server fell out you have 30 minutes left before Smart Client stops working and starts reporting invalid token."
You could say that when you set this you have a maximum time it will continue to work after a Management Server cut off, but you cannot know the precise time.