Closed chergert closed 6 years ago
Hmm, libvarlink uses epoll internally, so we use the matching EPOLL* definitions for the calls, but they are not exposed in the public header of the library.
Libvarlink stacks "poll file descriptors", which can only be done with epoll. How would changing the internal-only library code make things more portable, while we cannot really replace epoll in the currently used model anyway?
Clearly I didn't look into things that deep. In the end I switched to using GVariant over a pipe for a number of reasons. Since I don't need this anymore, closing.
I did a quick hack using libvarlink from the glib main loop and noticed in connection.c that things are using
EPOLLIN
andEPOLLOUT
constants fromsys/epoll.h
directly. Given that some projects will need to stay vaguely portable, is it worth modifying these to use the posixPOLLIN
/POLLOUT
?