Michael Tsai
AppleEventBridge: Native AppleScripting Support for Swift: http://mjtsai.com/blog/2015/07/14/appleeventbridge-native-applescripting-support-for-swift/ …
-
@ctp@optshiftk@mjtsai They were a really great idea at the time. Object-oriented IPC mechanisms are a Good Thing. But we have XPC now.
Jonathan Grynspan
Kyle S.
Chris Parker
@ctp @optshiftk @mjtsai So, for IPC, you should be using XPC, which is also object-oriented and which is much easier to work with.
-
-
@grynspan@ctp@optshiftk XPC is nice, but it doesn’t (yet?) work between apps. So it’s AE or nothing. -
@mjtsai@ctp@optshiftk It's geared toward services, but the mechanism is agnostic to the nature of each endpoint. You can run app-to-app. -
@grynspan Could you point to an example where the apps are peers? -
@mjtsai Not off the top of my head. You need a daemon or agent acting as a middleman and imposing security, but two apps can talk through it -
@grynspan That's what I thought, e.g. http://stackoverflow.com/questions/8637206/is-possible-to-use-mac-os-x-xpc-like-ipc-to-exchange-messages-between-processes … So I don't think this is a viable replacement for Apple events.
-
-
-
@grynspan@ctp@optshiftk@mjtsai OO message passing and IPC are not a good combo. http://jens.mooseyard.com/2009/07/05/The-Subtle-Dangers-Of-Distributed-Objects/ … -
@hhas01@ctp@optshiftk@mjtsai That looks like a critique of distributed objects, which are an old technology not used much anymore. - View other replies
-
-
- View other replies
-
@optshiftk@hhas01@ctp@mjtsai In fact, that describes NSXPCConnection. And the C API. It's all mach ports.
-
hhas
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.