ONVIF::...tPayload(3)

💅 ONVIF::...tPayload(3) — like, the User Contributed Perl Documentation page, bestie

okay so you clicked into the <pink>User Contributed Perl Documentation</pink> section (section 3, iykyk) and landed on ONVIF::Media::Types::ActionEngineEventPayload 🎀 — don't worry, it's way less scary than that name looks, I promise 🫶

---

✨ NAME ✨

ONVIF::Media::Types::ActionEngineEventPayload — bestie, that's literally the whole name, we move 💅

---

🌸 DESCRIPTION 🌸

So this is a Perl data type class for the XML Schema defined complexType ActionEngineEventPayload, and it lives in the namespace http://www.onvif.org/ver10/schema 🌈. Namespaces are just vibes with a URL, fr fr.

What even is an Action Engine Event Payload? It's a data structure that holds the info about ONVIF command invocations 👑. And here's the tea: because this event could get generated by other or proprietary actions, the command-invocation-specific fields are defined as optional, and there's an additional extension mechanism provided for future or additional action definitions ✨. It's giving "built for growth", it's giving main character energy 🌱.

🦋 PROPERTIES

These are the properties you can get to with the get_PROPERTY / set_PROPERTY methods — one bullet per property, no skipping, we don't do that here 😤:

• RequestInfo
• ResponseInfo
• Fault
• Extension

---

💜 METHODS 💜

🍓 new

The constructor, obviously 💅. The following data structure may be passed to new() — and yes, I'm giving it to you exactly as it is, character for character, because I would never do you dirty like that 😭:

{ # ONVIF::Media::Types::ActionEngineEventPayload
  RequestInfo =>  { # ONVIF::Media::Types::Envelope
    Header =>  { # ONVIF::Media::Types::Header
    },
    Body =>  { # ONVIF::Media::Types::Body
    },
  },
  ResponseInfo =>  { # ONVIF::Media::Types::Envelope
    Header =>  { # ONVIF::Media::Types::Header
    },
    Body =>  { # ONVIF::Media::Types::Body
    },
  },
  Fault =>  { # ONVIF::Media::Types::Fault
    faultcode =>  $some_value, # QName
    faultstring =>  $some_value, # string
    faultactor =>  $some_value, # anyURI
    detail =>  { # ONVIF::Media::Types::detail
    },
  },
  Extension =>  { # ONVIF::Media::Types::ActionEngineEventPayloadExtension
  },
},

Look at all those nested hashes — Envelope, Header, Body, Fault, detail, Extension — it's a whole little ecosystem in there 🧚. And peep the comments telling you the exact types: QName, string, anyURI ⭐.

---

🎀 AUTHOR 🎀

Generated by SOAP::WSDL — not a human, a generator, and honestly? Slay, it did that 🤖✨

---

okay so that's the whole page, you have literally every detail now, go forth and be iconic 💖

perl v5.42.3 🌸 · dated <yellow>1980-01-01</yellow> 🎀 · and that's the ONVIF::...tPayload(3) page, periodt 💅🦋