I'm currently implementing a library that I'd like to use to communicate with a UNIX domain socket (
/var/run/usbmuxd) - I had thought that NIO might be a good fit here, as it seems to wrap the required functionality that I'd need to spin up a socket connection and leave it alive for continued notifications and communication from that socket.
I can't find any great examples of how I would do this (or I'm misunderstanding the examples), and the docs assume a level of understanding that I don't yet have. I've had a look at things like the NIOChatClient, and that's great for sending a single request/response, but I can't work out how to keep the client running for continued communication.
Is this an appropriate use of NIO, or am I bending it into a shape it doesn't fit to? Can anyone offer advice on where I can look for more examples or info?