CosNaming(3)

💖 CosNaming 💖

okay bestie, welcome to the CosNaming page from the Erlang module definitions, aka the manual for a service that is literally just... a bunch of interfaces holding hands and deciding what naming means. iconic behavior fr fr 🎀

---

✨ NAME ✨

CosNaming — the CosNaming service is a whole collection of interfaces that, together, define the naming service. no cap, that's the entire vibe. 🦋

---

🌸 DESCRIPTION 🌸

so the naming service is the principal mechanism for clients to find objects in an ORB based world. like, that's its whole main character job. it hands you an initial naming context that functions as the root context for all names, and once you have that context, clients can navigate around in the name space. it's giving map app but for objects 🗺️✨

The types that are declared on the CosNaming level are, verbatim, bestie — do not touch, do not paraphrase:

typedef string Istring;
struct NameComponent {
      Istring id;
      Istring kind;
};

typedef sequence <NameComponent> Name;

enum BindingType {nobject, ncontext};

struct Binding {
      Name    binding_name;
      BindingType binding_type;
};

typedef sequence <Binding> BindingList;

And to get access to the record definitions for the structs, you use:

-include_lib("orber/COSS/CosNaming.hrl").

lowkey important: that include line is exactly that, character for character. don't be out here freehanding it 💅

Names are not an ORB object, but they can be structured in components, as seen by the definition above. and there are no requirements on names, so the service can support many different conventions and standards. truly inclusive, we love to see it 🌈

There are two different interfaces supported in the service:

• NamingContext
• BindingIterator

---

kisses, bestie 🫶 this page is brought to you by Ericsson AB, and it's from orber version 5.2.2, filed under the CosNaming(3) manual. go forth and name things, you got this 💜✨