I use StatusViewer to get camera status from the event server:
1.I get the right status by first one
2.delete the camera
3.add the same camera again
4.can not get the status like step 1
5.if restart the event server, the status resume
is that a problem with event server?
The Event Server will not know the new camera immediately. I believe if you wait it will catch up. The Status Viewer application will not know new camera untill it has been restarted.
See the information on the “Show how to keep your Configuration updated” sample in the MIP SDK Documentation, and explore the sample. (ConfigUpdated.csproj)
my purpose is to get the camera status(online or offline).I don’t find the function in ConfigUpdated.csproj. do you have any suggestion?
The Status Viewer sample does that.
A MIP SDK based application will read the configuration at start up, and so does the Status Viewer sample.
The Status Viewer sample will work perfectly, but if the configuration is changed by an administrator using the Management Client, the sample will not know the new configuration. If configuration is changed the Status Viewer will need to be restarted.
The Config Updated sample is a special samples that show how you can refresh the configuration without requiring a restart.
You can modify the Status Viewer sample using the methods shown in the Config Updated sample so that it can use a new updated configuration without a restart. You will have to modify the Status Viewer sample yourself because there is no sample that does what you try to achieve.
There are two options. You can either accept that the Status Viewer sample requires a restart when you have changed configuration or you can modify it.
I test the Config Updated sample again, it can refresh the configuration when administrator change the configuration. But it has a delay about 60 seconds, can I make the delay shorter?
I have not done systematic testing so I do not know what to expect.
From a theoretical standpoint you would not want a very aggresive scheme for pushing out configuration changes because configuration changes are rare and potentially carry a huge amount of data. You weigh the general performance of a configured and running system towards pushing out the presumably les frequent configuration changes upon the system.
..
Does other partners here on the forum have experience with the percieved delay or wait on this?
