COSNOTIFYCOMM_NOTIFYSUBSCRIBE(3erl)

🌸 NAME 🌸

CosNotifyComm_NotifySubscribe — bestie, this module is the whole implementation of the OMG CosNotifyComm::NotifySubscribe interface. iconic behavior tbh 💅

---

✨ DESCRIPTION ✨

okay so first things first: to get access to the record definitions for the structures, you're gonna use this include, and yes it goes in your code exactly like this:

-include_lib("cosNotification/include/*.hrl").

and lowkey the vibe here is: all objects that inherit this interface export the functions described in this module. every single one. no gatekeeping 🫶

---

👑 EXPORTS 👑

subscription_change(Object, Added, Removed) -> Reply

the main character function, fr fr. let's break down the types:

• Object = #objref — the object reference, the lil handle to the thing ✨
• Added = Removed = EventTypeSeq — both of these are event type sequences, matching energy 💖
• EventTypeSeq = [type] — literally just a list of types
• Reply = ok | {'EXCEPTION', CosNotifyComm_InvalidEventType{type}} — so you either get a chill ok, or you get an exception tuple wrapped around CosNotifyComm_InvalidEventType{type} 😭
• type = #'CosNotification_EventType'{domain_name, type_name} — a record with a domain_name and a type_name
• domain_name = type_name = string() — both of these are strings, periodt 🎀

so what does this operation actually do? it takes as input two sequences of event type names:

1. the events the client will accept in the future 🌈
2. the events the client will not accept in the future 🙈

respectively. like, in that order. yes it matters. slay 💅

---

so yeah, that's the whole page bestie — go forth and subscribe to your events responsibly 🦋✨

this was brought to you by Ericsson AB, from the cosNotification 5.2.2 era, and it's the CosNotifyC...fySubscribe(3) page, mwah 💖