ONVIF:...tions2(3pm)

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

πŸ’– NAME πŸ’–

ONVIF::Device::Types::H264Options2 β€” bestie, this is the whole vibe of this page, no cap.


🌸 DESCRIPTION 🌸

Okay so picture this: it's a Perl data type class, right? And it exists for exactly one reason β€” to be the Perl lil' stand-in for the XML Schema defined complexType called H264Options2.

And where does that complexType live? In the namespace http://www.onvif.org/ver10/schema. That's it, that's the whole lore. πŸ¦‹

✨ PROPERTIES ✨

These are the properties you can get at, and the way you get at them is via the get_PROPERTY / set_PROPERTY methods. That's the pattern, iykyk.

  • BitrateRange β€” yep, that's the one. The only one. She's solo and she's iconic. πŸ‘‘

πŸŽ€ METHODS πŸŽ€

πŸ’… new

Constructor, periodt. It's the thing that makes a new one of these.

And here's the data structure you may pass to new(), copied exactly, not a single character touched, because we do not play with literals around here:

{ # ONVIF::Device::Types::H264Options2
  BitrateRange =>  { # ONVIF::Device::Types::IntRange
    Min =>  $some_value, # int
    Max =>  $some_value, # int
  },
},

Look at that nesting. BitrateRange holding an ONVIF::Device::Types::IntRange, which is holding a Min and a Max, both of them ints, both of them literally written as $some_value because that's your job to fill in, not ours. Slay. 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL β€” not hand-written, not vibed into existence, generated. Respect the machine that birthed her. ⭐


And that's the whole page, bestie!</purl> Wait, typo, my bad β€” that's the whole page, bestie! 🌈 This gorgeous little document came to you from perl v5.40.1 and it's dated 2026-02-01, so go forth, get_PROPERTY responsibly, and remember: BitrateRange stays winning. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from