ONVIF:...ension(3pm)

✨ NAME ✨

ONVIF::Analytics::Types::SecurityCapabilitiesExtension — bestie, that's the whole name, and yes it's a mouthful 💅 (it lives in the User Contributed Perl Documentation corner of the perl manual, section 3pm, if you were wondering where we are rn 🫶)

---

🌸 DESCRIPTION 🌸

okay so. This is a Perl data type class. That's it, that's the gig ✨

It represents the XML Schema defined complexType SecurityCapabilitiesExtension, and it comes from the namespace http://www.onvif.org/ver10/schema. No cap, that's literally its whole personality 💖

---

💜 PROPERTIES 💜

These properties? You get to them with the get_PROPERTY / set_PROPERTY methods. Iconic access pattern, we love to see it 🌈

• TLS1__0 — okay so listen. The name of this property has been altered, because it didn't match perl's notion of variable/subroutine names 😭 The altered name is used in perl code only — XML output uses the original name, which is:

TLS1.0

• Extension — yes. That's the property. She's here, she's named Extension, slay 🦋

---

🎀 METHODS 🎀

✨ new ✨

Constructor, bestie 🫶 The following data structure may be passed to new():

{ # ONVIF::Analytics::Types::SecurityCapabilitiesExtension
  TLS1__0 =>  $some_value, # boolean
  Extension =>  { # ONVIF::Analytics::Types::SecurityCapabilitiesExtension2
    Dot1X =>  $some_value, # boolean
    SupportedEAPMethod =>  $some_value, # int
    RemoteUserHandling =>  $some_value, # boolean
  },
},

look at that nesting. Extension opens up into a whole ONVIF::Analytics::Types::SecurityCapabilitiesExtension2 situation with Dot1X (boolean), SupportedEAPMethod (int) and RemoteUserHandling (boolean). it's giving structure. it's giving schema. periodt 💅

---

👑 AUTHOR 👑

Generated by SOAP::WSDL 💖

---

and that's the whole page, no notes 🎀

perl v5.40.1 · 2026-02-01 · ONVIF:...ension(3pm) — mwah, bye bestie, go build something iconic 💜✨