In socket programming, what is usually called the entity that receives socket messages? My socket class is called “EventHandler” and I hate that name a lot. 😅
@brunoph transmitter/receiver?
@brunoph Call it SocketListener if it's for a single listening socket.
Otherwise, if it's just the place where you call poll() for all your fds, typical names are: EventLoop, MainLoop, Dispatcher, Reactor...
@brunoph By the way, designing a scalable, multi-threaded, portable event loop is tricky. Consider taking one of these solutions (or at least study them):
https://libuv.org/
https://libevent.org/
https://doc.qt.io/qt-5/qeventloop.html
https://developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html
@codewiz Thank you! And absolutely, I’m using Starscream. I wouldn’t trust myself to write socket code. 😝
I was just wondering what kind of names were usual because I couldn’t come up with anything that I liked, but what I’m implementing is the higher, business-logic level code.
@brunoph I'd call it a "listener".
I’m almost going with “antenna” for the individual socket listener entity and “radio” for the entity that controls all the entities of “antenna” lol