sockets(3)

💖 sockets — the manual, but make it a group chat 💖

okay so this is sockets(3), from the Library Functions Manual, and it's literally all about the underlying transport protocol socket classes. yes bestie, the plumbing. the ✨vibes✨ underneath your RTP stack. sit down, hydrate, let's go 🫶

---

✨ NAME ✨

sockets — the underlying transport protocol socket classes. that's it, that's the whole name section, she's short and she knows it 💅

---

🌸 SYNOPSIS 🌸

🎀 Classes 🎀

• class RTPBaseUDPIPv4Socket — a UDP/IPv4 socket class that is targeted at RTP stacks. she's built for this specific job and nothing else, iconic behavior honestly 👑
• class DualRTPChannel< BaseSocket > — a templated channel thing that takes a BaseSocket. no further notes in the original, she's mysterious, we respect that 🙈
• class DualUDPIPv4Socket — a socket class that is based on two UDP/IPv4 sockets. two. a duo. a dynamic duo. no cap 🔥

🦋 Typedefs 🦋

typedef DualRTPChannel< RTPBaseUDPIPv4Socket > DualRTPUDPIPv4Channel
typedef RTPBaseUDPIPv4Socket SingleRTPChannel
typedef SingleRTPChannel SymmetricRTPChannel

• DualRTPUDPIPv4Channel — the DualRTPChannel< RTPBaseUDPIPv4Socket > combo. yes it's a mouthful, yes it slays 💅
• SingleRTPChannel — it's just RTPBaseUDPIPv4Socket. and the original says: may be used in applications where using the same socket for both sending and receiving is not a limitation. so like, if one socket doing both jobs is fine for you, this is your girl ✨
• SymmetricRTPChannel — it's a SingleRTPChannel. and the original is out here being cute: actually, RTP with a single channel can be called 'Symmetric RTP'. the way that the docs just casually dropped a whole naming convention on us 😭💖

---

🧚 Detailed Description 🧚

so... this section exists. the original has a heading for it and then just moves right along to the next thing. no content. zero. a blank canvas. main character energy with no dialogue, honestly 💀

we are not skipping it though. we would never. it's here, it's got a heading, and it's got exactly as much in it as the original gave us: nothing but the title 🌸

---

💜 Typedef Documentation 💜

⭐ typedef DualRTPChannel<RTPBaseUDPIPv4Socket> DualRTPUDPIPv4Channel

that's the whole entry. the declaration and a bow on top. we move on 🎀

⭐ typedef RTPBaseUDPIPv4Socket SingleRTPChannel

the original says, and I quote (in my own words, but like, faithfully): may be used in applications where using the same socket for both sending and receiving is not a limitation.

so if sharing one socket for send AND receive isn't a problem for your app? this is the one. periodt. 💅

⭐ typedef SingleRTPChannel SymmetricRTPChannel

and the note here, again lovingly paraphrased from the source: actually, RTP with a single channel can be called 'Symmetric RTP'.

like. they just named it that. because it's symmetric. it's giving self-aware documentation and I am obsessed 🦋

---

👑 Author 👑

Generated automatically by Doxygen for ccRTP from the source code.

so yeah, no human author to thank here — Doxygen did the whole thing. a robot wrote our girl's manual and honestly? she ate and left no crumbs 🤖💖

---

okay bestie that's the whole page, every single class, every single typedef, every single one-line description, all present and accounted for, fr fr 🌈

this little love letter to sockets(3) came to you straight from the ccRTP source, brought to life by Doxygen, and it lives in the sockets(3) section of your friendly neighbourhood manual pages. now go read the source and slay 💅✨