ConflictHa...ortAddress(3)

💖 ConflictHandler::ConflictingTransportAddress — NAME 💖

okay bestie, gather round, because this one is literally a whole little class called ConflictHandler::ConflictingTransportAddress and it lives in the Library Functions Manual, section 3. it's giving "I track a network address plus its ports and I'm not sorry about it" energy. 💅

---

✨ SYNOPSIS ✨

first things first, you gotta pull it in:

#include <iqueue.h>

🫶 Public Member Functions

• ConflictingTransportAddress (InetAddress na, tpport_t dtp, tpport_t ctp) — the constructor, she builds the whole thing from a network address and two transport ports, no cap.
• void setNext (ConflictingTransportAddress *nc) — hands her a pointer to the next one in the chain, so she can link up with her girls.
• const InetAddress & getNetworkAddress () const — hands you back the network address, by reference, and she's not letting you touch it (const bestie, respect the boundaries).
• tpport_t getDataTransportPort () const — gives you the data transport port, and no, you can't edit it.
• tpport_t getControlTransportPort () const — gives you the control transport port, same deal, read-only queen.

🎀 Public Attributes

• InetAddress networkAddress — the address itself, sitting right there in the open.
• tpport_t dataTransportPort — the data transport port, public and proud.
• tpport_t controlTransportPort — the control transport port, also out in the open.
• ConflictingTransportAddress * next — pointer to the next ConflictingTransportAddress in the lineup. it's giving linked list. 🔗
• timeval lastPacketTime — when the last packet showed up, timestamped and everything.

---

🌸 Constructor & Destructor Documentation 🌸

💖 ConflictHandler::ConflictingTransportAddress::ConflictingTransportAddress

(InetAddress na, tpport_t dtp, tpport_t ctp)

that's the whole signature, that's the whole vibe. you give her na, dtp, and ctp, and she exists now. iconic behaviour honestly.

---

🦋 Member Function Documentation 🦋

• tpport_t ConflictHandler::ConflictingTransportAddress::getControlTransportPort () const [inline] — inline, const, and fully committed to giving you the control transport port. she's fast because she's [inline], periodt.
• tpport_t ConflictHandler::ConflictingTransportAddress::getDataTransportPort () const [inline] — same energy, different port: this one returns the data transport port, [inline] and const as always. 💫
• const InetAddress & ConflictHandler::ConflictingTransportAddress::getNetworkAddress () const [inline] — returns a const reference to the InetAddress, [inline], so you get the address without the copy and without the ability to mess with it. boundaries, bestie.
• void ConflictHandler::ConflictingTransportAddress::setNext (ConflictingTransportAddress * nc) [inline] — takes a pointer nc to another ConflictingTransportAddress and sets it as the next one. [inline], void, no notes, ate. 🔥

---

🌈 Member Data Documentation 🌈

• tpport_t ConflictHandler::ConflictingTransportAddress::controlTransportPort — the control transport port, stored as a tpport_t.
• tpport_t ConflictHandler::ConflictingTransportAddress::dataTransportPort — the data transport port, also a tpport_t.
• timeval ConflictHandler::ConflictingTransportAddress::lastPacketTime — a timeval holding the last packet time. time is fake but this field is real. ⏰
• InetAddress ConflictHandler::ConflictingTransportAddress::networkAddress — the InetAddress for this entry.
• ConflictingTransportAddress* ConflictHandler::ConflictingTransportAddress::next — a pointer to the next ConflictingTransportAddress. chain them together and you've got yourself a whole squad. 👑

---

👑 Author 👑

Generated automatically by Doxygen for ccRTP from the source code.

---

and that's the whole page, bestie — ccRTP version vibes, manual section 3, shipped straight from the Library Functions Manual era. no cap, you now know her better than she knows herself. go forth and link some ConflictingTransportAddresses. 🎀💖✨