If only a true socket is selectable, then I will likely have to approach it that way.
I was hoping that I could just have one object, to which I could write, and then read what I just wrote. By using normal sockets, I'll have to put together a pair of them, and in order to do that, I'll have to set one up for listen mode and then accept() on it. I think that I'll have to be multithreaded to do that, which I've managed to avoid thus far. That, if nothing else, is the reason why I'm not eager to bite the bullet.
Perhaps I should ask a different question... is there a way (without multithreading) to connect two sockets to talk to each other?
If I could work that bit of magic, then I could make a class that looks like just one object, but I could sysread() on one socket and syswrite() on the other, giving the appearance of a loopback or echoing socket.
| [reply] |