ONVIF:...esponse(3pm)

πŸ“¦
version 1.36.37 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– ONVIF::Media::Elements::GetMetadataConfigurationsResponse πŸ’–

okay bestie, sit down, we're doing Perl SOAP stuff and honestly? it's giving ✨structured data✨. this is a page from the User Contributed Perl Documentation collection, and the module we're stanning today is ONVIF::Media::Elements::GetMetadataConfigurationsResponse. yes the name is long. no we're not shortening it. periodt. πŸ’…


🌸 NAME 🌸

ONVIF::Media::Elements::GetMetadataConfigurationsResponse β€” literally the whole name is right there, she's not hiding 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

so like, this is a Perl data type class for the XML Schema defined element called GetMetadataConfigurationsResponse, and that element lives in the namespace http://www.onvif.org/ver10/media/wsdl. that's it. that's the vibe. it's a Perl class that exists so you can build and read this one XML element without losing your entire mind 😌✨


πŸŽ€ PROPERTIES πŸŽ€

these are the properties you can touch, and you touch them with get_PROPERTY / set_PROPERTY methods β€” classic Perl setup, we love a consistent interface πŸ’–

  • Configurations β€” the one and only property on this element, and here's exactly how you poke at her:
$element->set_Configurations($data);
$element->get_Configurations();

like, set it, get it, iconic behavior honestly πŸ‘‘


🧚 METHODS 🧚

🌈 new

my $element = ONVIF::Media::Elements::GetMetadataConfigurationsResponse->new($data);

this is the constructor, bestie. she makes you a brand new element. and here's the data structure you're allowed to pass into new() β€” every single field, no skips, no cuts, we keep it ALL fr fr:

{
  Configurations =>  { # ONVIF::Media::Types::MetadataConfiguration
    PTZStatus =>  { # ONVIF::Media::Types::PTZFilter
      Status =>  $some_value, # boolean
      Position =>  $some_value, # boolean
    },
    Analytics =>  $some_value, # boolean
    Multicast =>  { # ONVIF::Media::Types::MulticastConfiguration
      Address =>  { # ONVIF::Media::Types::IPAddress
        Type => $some_value, # IPType
        IPv4Address => $some_value, # IPv4Address
        IPv6Address => $some_value, # IPv6Address
      },
      Port =>  $some_value, # int
      TTL =>  $some_value, # int
      AutoStart =>  $some_value, # boolean
    },
    SessionTimeout =>  $some_value, # duration
    AnalyticsEngineConfiguration =>  { # ONVIF::Media::Types::AnalyticsEngineConfiguration
      AnalyticsModule =>  { # ONVIF::Media::Types::Config
        Parameters =>  { # ONVIF::Media::Types::ItemList
          SimpleItem => ,
          ElementItem =>  {
          },
          Extension =>  { # ONVIF::Media::Types::ItemListExtension
          },
        },
      },
      Extension =>  { # ONVIF::Media::Types::AnalyticsEngineConfigurationExtension
      },
    },
    Extension =>  { # ONVIF::Media::Types::MetadataConfigurationExtension
    },
  },
},

look at all those nested hashes. it's giving ✨layers✨. it's giving onion. it's giving "why is there an Extension inside an Extension" and honestly? we don't ask questions, we just fill in the values πŸ« πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL β€” yes girl, nobody hand-wrote this, the machine did it, and the machine ate πŸ’…βœ¨


aaaand that's the whole page, bestie! this one came to you from the User Contributed Perl Documentation, documented for perl v5.40.1, dated 2026-02-01. go forth and configure your metadata, you absolute main character πŸ¦‹πŸ’–πŸŽ€

πŸ“¦ where this page comes from