I noticed that the Image Server (TCP/XML) API is marked as “Legacy”, does that mean we should use WebRTC as the preferred method; i.e. will the Image Server (TCP/XML) API become deprecated in the future?
https://doc.developer.milestonesys.com/mipvmsapi/api-overview/integrations/video-audio-metadata/
A second related question – is WebRTC more performant (network traffic & speed) than using the Image Server TCP/XML socket version of the Image Server API?
Currently the Image Server protocol is used by all other methods and APIs, including WebRTC. Underneath everything else, this protocol, which is also called legacy because it is not SOAP (but very SOAP-like), is very core to video extraction in XProtect. There are ongoing discussions how to replace this core protocol with something more modern and rest assured that we will announce it when it eventually happens.
It will not become deprecated in the near future. Any deprecation will be announced, and the announcement will come with information how to best handle it.
As WebRTC uses Image Server underneath, the answer to your second question must be no.
Hi Bo,
Thanks very much for the quick & informative answer! Sounds like we’re good to go w/our plan on using the Image Server (TCP/XML) API.