RTDSERVER(1)

🌸 RTDSERVER — image event dispatcher for RTD 🌸

okay so bestie, this is rtdServer(1), a User Commands page, and it's literally the group chat admin of image events. let's get into it 💅

✨ NAME ✨

rtdServer — image event dispatcher for RTD

🎀 SYNOPSIS 🎀

rtdServer [-v] [-p] [-s]

💖 DESCRIPTION 💖

so rtdServer is the process that manages the image event mechanism, and it is the main character here, no cap.

Clients register to the rtdServer via the rtdInitImageEvt call. When a client attaches to a camera source, an incoming image event will be forwarded to this client. Several clients can attach to the same camera source, because multicasting of event notification is supported by the rtdServer — she's a sharer, she's generous, she's iconic 🫶. Image events received from image sources where no clients are attached are simply discarded (thrown away, ghosted, left on read 💀). Clients can also attach to image sources that not have registered yet, because the rtdServer supports a independence between image event producer and image event consumer. lowkey unbothered, highkey powerful ✨

Furthermore, rtdServer contains a simulator part that can be used to simulate the generation of image events. This feature is reserved for testing purposes only — do not make it your whole personality fr fr. Similarly, it also contains a performance test facility, in which several areas of shared memory are sent to a client Rtd in quick succession, and measurements are taken on certain performance parameters (see RtdPerformanceTool(3/n)).

The rtdServer also implements semaphore locking of shared memory, to avoid the possibility of the RTD client reading the shared memory at the same time as the CCD writes (this is known as "image jitter"). The server program expects the CCD software to set a semaphore against any shared memory that has been written to (effectively to lock it). The server will then increment this semaphore by the number of RTD clients less one. If semaphores are not implemented in the incoming image event, no action is taken. The overall locking scheme is discussed in more detail in rtdSem(1). Semaphore locking is implemented in the simulator facility. so yeah, she locks things down like a girl who knows her boundaries 💅

the options, bestie

• -v — verbose mode. she talks more. we love a chatty queen 🗣️
• -p — port number, default 5555. Set with RTD_SERVER_PORT ✨
• -t — delay between image events in msec (default 5) ⏱️

side note bestie: -s shows up in the synopsis up top, so don't act surprised when you see it in the wild 👑 🙈

🌈 SEE ALSO 🌈

• rtd(1)
• rtdClient(1)
• rtcCubeClient(1)

and that's the whole page, bestie — no notes, she ate 💖

this one's from the RTDSERVER source, version dated March 2009, and it's filed under RTDSERVER(1). go forth and dispatch those image events, you gorgeous little RTD client 🦋✨🎀