ONVIF::...uration(3)
β¨ NAME β¨
okay bestie so sit down, hydrate, and let me introduce you to ONVIF::Device::Types::AnalyticsDeviceEngineConfiguration π β that's the whole mouthful, yes, iykyk. You probably clicked in from ONVIF::...uration(3) in the User Contributed Perl Documentation (the truncated little gremlin of a page title π), and honestly? you've arrived exactly where you needed to be.
This is a Perl data type class for the XML Schema defined complexType AnalyticsDeviceEngineConfiguration from the namespace http://www.onvif.org/ver10/schema. That's it, that's the whole gig. It's giving "yes I am a type class, and I am iconic for it" π
πΈ DESCRIPTION πΈ
So, our main character here is a Perl data type class representing the XML Schema complexType AnalyticsDeviceEngineConfiguration from the namespace http://www.onvif.org/ver10/schema. No cap, that's the entire assignment. It's a little type class doing its little type class job and we respect it π«Ά
π PROPERTIES π
The following properties may be accessed using get_PROPERTY / set_PROPERTY methods β that's the whole vibe, get it and set it, slay β¨
EngineConfigurationβ yes bestie, this one is the star of the show, it's the engine configuration itself π₯Extensionβ and the classic extension slot, because there's always room for more, lowkey π
π METHODS π
β new β
Constructor!! π new is the one that spins up your whole object. And here's the tea β the following data structure may be passed to new() βοΈ:
{ # ONVIF::Device::Types::AnalyticsDeviceEngineConfiguration
EngineConfiguration => { # ONVIF::Device::Types::EngineConfiguration
VideoAnalyticsConfiguration => { # ONVIF::Device::Types::VideoAnalyticsConfiguration
AnalyticsEngineConfiguration => { # ONVIF::Device::Types::AnalyticsEngineConfiguration
AnalyticsModule => { # ONVIF::Device::Types::Config
Parameters => { # ONVIF::Device::Types::ItemList
SimpleItem => ,
ElementItem => {
},
Extension => { # ONVIF::Device::Types::ItemListExtension
},
},
},
Extension => { # ONVIF::Device::Types::AnalyticsEngineConfigurationExtension
},
},
RuleEngineConfiguration => { # ONVIF::Device::Types::RuleEngineConfiguration
Rule => { # ONVIF::Device::Types::Config
Parameters => { # ONVIF::Device::Types::ItemList
SimpleItem => ,
ElementItem => {
},
Extension => { # ONVIF::Device::Types::ItemListExtension
},
},
},
Extension => { # ONVIF::Device::Types::RuleEngineConfigurationExtension
},
},
},
AnalyticsEngineInputInfo => { # ONVIF::Device::Types::AnalyticsEngineInputInfo
InputInfo => { # ONVIF::Device::Types::Config
Parameters => { # ONVIF::Device::Types::ItemList
SimpleItem => ,
ElementItem => {
},
Extension => { # ONVIF::Device::Types::ItemListExtension
},
},
},
Extension => { # ONVIF::Device::Types::AnalyticsEngineInputInfoExtension
},
},
},
Extension => { # ONVIF::Device::Types::AnalyticsDeviceEngineConfigurationExtension
},
},
okay look at all those nested hashes π it's giving matryoshka dolls, it's giving onion layers, it's giving "I have a VideoAnalyticsConfiguration, which has an AnalyticsEngineConfiguration, which has an AnalyticsModuleβ¦" β literally the Russian nesting dolls of Perl data structures πͺ but honestly? the comments tell you exactly which type each hash belongs to, so you're never lost bestie, you've got this πͺ
π quick vibe check: the nesting is deep βEngineConfigurationβVideoAnalyticsConfigurationβAnalyticsEngineConfigurationβAnalyticsModuleβParametersβSimpleItem/ElementItem/Extension. Copy the shape exactly as shown, don't get creative with it, fr fr.
π AUTHOR π
Generated by SOAP::WSDL β¨ β that's the whole author note, it was built by the machine, no humans credited, main character energy fr π§
and that's the whole page, bestie π no notes, periodt. this masterpiece of autogenerated documentation lives on perl v5.42.3 and is dated 1980-01-01 (yes, the actual first day of 1980, iconic timestamp behavior π
) β okay love you bye ππ
π¦ where this page comes from
- nixpkgs unstable: zoneminder 1.38.6
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms