sources(3)

πŸ“¦
version 2.0.9 Β· 4 versions
, in debian trixie, ubuntu noble, ubuntu questing

πŸ’– sources(3) β€” Library Functions Manual πŸ’–

okay bestie, buckle up, this is the Library Functions Manual page for sources, and it's all about Participants and synchronization sources. yes that's the NAME line, we're going full send. 🫢


✨ NAME ✨

sources β€” Participants and synchronization sources. πŸ’…


🌸 SYNOPSIS 🌸

πŸŽ€ Classes

  • class SDESItemsHolder β€” holds the SDES items and related information from a participant in an RTP application. it's giving keeper-of-the-metadata, fr fr. πŸ“
  • class Participant β€” a class of objects representing remote participants (RTP applications) in a multimedia session. the whole squad, basically. πŸ‘‘
  • class SyncSource β€” synchronization source in an RTP session. yes queen, sync. ✨
  • class RTPApplication β€” an RTP application, holding identifying RTCP SDES item values. main character energy, lowkey. πŸ¦‹

πŸ’œ Functions

__EXPORT RTPApplication & defaultApplication ()
  • __EXPORT RTPApplication & defaultApplication () β€” get the RTPApplication object for the 'default' application (the only one used by common applications -those that only implement one 'RTP application'). we'll spill the tea on this one in a sec. πŸ«–

πŸ”₯ Detailed Description πŸ”₯

so… that's literally it. the detailed description section is just the header, no extra lore. the real gossip lives in the function docs below. πŸ’€ not the empty section, bestie, i know. πŸ™ˆ


⭐ Function Documentation ⭐

🌈 __EXPORT RTPApplication & defaultApplication ()

okay so this one is the function. here's the whole vibe: it gets you the RTPApplication object for the 'default' application (the only one used by common applications -those that only implement one 'RTP application'). 🎯

and here's the part that's actually iconic β€” this application object is different from all the others that may be defined, because:

  • it is automatically constructed by the ccRTP stack, no manual labour required πŸ’…
  • its CNAME is automatically assigned (as user@host) πŸ‘‘

whereas the other application objects' CNAME is provided to its constructor. so like… they gotta bring their own name to the party, this one got dressed by ccRTP itself. periodt. πŸŽ€

not me being obsessed with auto-assigned CNAMEs. iykyk. 🧚

🌟 Examples

these bad boys use it: ccrtptest.cpp, rtphello.cpp, rtplisten.cpp, and rtpsend.cpp. go look, bestie, they're right there. πŸ”₯


πŸ’œ Author πŸ’œ

Generated automatically by Doxygen for ccRTP from the source code. yes, a robot wrote it, and honestly? it ate. πŸ€–βœ¨


and that's the whole page! shoutout to ccRTP for the sources(3) glow-up, straight outta the Library Functions Manual. ily, go read the other pages, mwah. πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from