XPC.which IPC mechanism is recommended ?
No. While UNIX domain sockets are supported on macOS, and in some circumstances they are the right choice, in most cases you should do IPC using XPC.is socket communication good for the same ?
For NE, declare a Mach service using NEMachServiceName. For ES, you’d use NSEndpointSecurityMachServiceName.howz the setting up different in NetworkExtension & EndpointSecurity ?
Yes.should we just connect from the app to this NEMachServiceName and then start exchanging message.
No, that’s a really bad idea. The problem is that this is a dependency inversion. In general, apps should call daemons. If you try to do it the other way around, you inevitably run into problems. For example, in a fast user switched environment, with multiple users running your app simultaneously, which one would the daemon connect to?was just curious whether I create the listener in the app and connect (from client) from the Network Extension. is it a good idea ?
Is there something similar for EndpointSecurity?
No. While ES system extension are effectively launchd daemons under the covers, you don’t have direct control over their launchd property list file.
Having said that, setting up the listening socket via the launchd property list file is only relevant if you want to support starting on demand. For an ES sysex, which is always started, there’s no benefit to that, so you could just as easily create your listening socket as your sysex starts up. The only gotcha is that, if the client starts up before you, it won’t wait for you to start, so you’ll need some retry logic on the client side.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"