get profiles response and videoanalytics configuration

[sujithhanwha]

When several rules and analytics modules are configured on the device, Getprofiles response is becoming huge because of the analytics configuration attached to the profile and if analytics configuration is attached to all profiles of a particular video source. Then this repeats for all profiles.

Its the same case for both media1 and media2 (here at least we have filtering option, but still requires a solution)

Would be better to mention that in get profiles response, only videoanalytics configuration token, name and usecount are required and we need not list all the configured rules and analytics module.

[HansBusch]

For media2 I don't see any necessity, since clients can control information.

For media1 leaving the information out may break client implementations. However the likelihood is very small.

For a typical sample with three rules need 1.8kByte which compresses to 0.6k. A multi imager with each of four lines having three profiles may end up with about 64k. However the zipped size is much less about 2k due to repeated content.

Note that the following elements are mandatory:

• AnalyticsEngineConfiguration
• RuleEngineConfiguration

Making them optional would break parses. So only possibility is to not provide content. Note that a similar issue exists with MetadataConfiguration.

Agree with the problem description, but hesitate to generally remove the requirement. Maybe we should restrict it to multi-channel devices.

[kieran242]

I am in agreement with Hans and would not be in favour of modifying the Media 1 profiles response. I have worked with MultiSensor camera devices supporting Media 1 specification only in JCI Client and found a need for parsing of the information.

[kieran242]

As PR #250 created are we able to close.

[sujithhanwha]

yes we can close this since PR #250 handles this.