ONVIF::...esponse(3)

πŸ“¦ version 1.38.6, in nixpkgs unstable

✨ ONVIF::...esponse(3) ✨

okay so bestie, this page is from the User Contributed Perl Documentation and it's literally all about ONVIF::Device::Elements::GetServicesResponse πŸ’… don't let the long name scare you, it's giving very niche Perl XML energy and we're gonna get through it together 🫢


🌸 NAME 🌸

ONVIF::Device::Elements::GetServicesResponse

πŸ¦‹ DESCRIPTION πŸ¦‹

It's a Perl data type class for the XML Schema defined element GetServicesResponse from the namespace http://www.onvif.org/ver10/device/wsdl. That's the whole vibe ✨

πŸŽ€ PROPERTIES πŸŽ€

The following properties may be accessed using get_PROPERTY / set_PROPERTY methods:

  • Service β€” your service data lives here, and you get at it like this:
$element->set_Service($data);
$element->get_Service();

πŸ’œ METHODS πŸ’œ

🌈 new

my $element = ONVIF::Device::Elements::GetServicesResponse->new($data);

Constructor πŸ› οΈ The following data structure may be passed to new():

{
  Service =>  { # ONVIF::Device::Types::Service
    Namespace =>  $some_value, # anyURI
    XAddr =>  $some_value, # anyURI
    Capabilities =>  {
    },
    Version =>  { # ONVIF::Device::Types::OnvifVersion
      Major =>  $some_value, # int
      Minor =>  $some_value, # int
    },
  },
},

Like, look at that nested structure β€” it's giving little XML family tree 🌳 and yes, Capabilities is just an empty hash in this example, no cap, that's exactly how it's written 🧚

πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL β€” iconic, automated, doing its thing ✨


okay that's the whole page, bestie πŸ’– no missing flags, no mystery extras, just the class, the Service property, the constructor data structure, and the author note. slay.

signing off with the classic manpage footer energy: perl v5.42.3 and the date 1980-01-01 πŸŽ€πŸ’…βœ¨

πŸ“¦ where this page comes from