Intercommunication between to macOS apps on local Mac
Is there an easy way, in Swift, for one macOS app to send a message to another macOS app on the same mac (localhost). I have two macOS apps, one of them is a menu app. There are some situations the standard macOS app need to send a notification (a one way ticket, fire and forget) to the menu app.
swift
asked Nov 23 '18 at 17:09
TevensenTevensen
165
add a comment |
Is there an easy way, in Swift, for one macOS app to send a message to another macOS app on the same mac (localhost). I have two macOS apps, one of them is a menu app. There are some situations the standard macOS app need to send a notification (a one way ticket, fire and forget) to the menu app.
swift
asked Nov 23 '18 at 17:09
TevensenTevensen
165
add a comment |
Is there an easy way, in Swift, for one macOS app to send a message to another macOS app on the same mac (localhost). I have two macOS apps, one of them is a menu app. There are some situations the standard macOS app need to send a notification (a one way ticket, fire and forget) to the menu app.
swift
asked Nov 23 '18 at 17:09
TevensenTevensen
165
Is there an easy way, in Swift, for one macOS app to send a message to another macOS app on the same mac (localhost). I have two macOS apps, one of them is a menu app. There are some situations the standard macOS app need to send a notification (a one way ticket, fire and forget) to the menu app.
swift
swift
asked Nov 23 '18 at 17:09
TevensenTevensen
165
asked Nov 23 '18 at 17:09
TevensenTevensen
165
asked Nov 23 '18 at 17:09
TevensenTevensen
165
asked Nov 23 '18 at 17:09
TevensenTevensen
165
asked Nov 23 '18 at 17:09
TevensenTevensen
165
165
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There are dozens of different options of how to achieve this. Each with their own advantages and disadvantages.
Probably the easiest is sending notifications using the DistributedNotificationCenter from Foundation. It’s just like the regular NotificationCenter but across Process-Boundaries.
On the receiving side you register an observer like this:
DistributedNotificationCenter.default().addObserver(forName: NSNotification.Name("com.mycompany.MyNotification"), object: nil, queue: nil) { notification in
print(notification)
}
On the sending side you post a notification like this:
DistributedNotificationCenter.default().post(name: NSNotification.Name("com.mycompany.MyNotification"), object: nil, userInfo: ["data": "to send"])
This is not very secure though - any process can send and receive those notifications. So if they contain private data you shouldn't use this method. This also means you should use a unique notification name. Good idea to start that with a reversed DNS name like com.mycompany. here.
If your app is sandboxed there is another limitation that you cannot send an userInfo dictionary.
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450639%2fintercommunication-between-to-macos-apps-on-local-mac%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are dozens of different options of how to achieve this. Each with their own advantages and disadvantages.
Probably the easiest is sending notifications using the DistributedNotificationCenter from Foundation. It’s just like the regular NotificationCenter but across Process-Boundaries.
On the receiving side you register an observer like this:
DistributedNotificationCenter.default().addObserver(forName: NSNotification.Name("com.mycompany.MyNotification"), object: nil, queue: nil) { notification in
print(notification)
}
On the sending side you post a notification like this:
DistributedNotificationCenter.default().post(name: NSNotification.Name("com.mycompany.MyNotification"), object: nil, userInfo: ["data": "to send"])
This is not very secure though - any process can send and receive those notifications. So if they contain private data you shouldn't use this method. This also means you should use a unique notification name. Good idea to start that with a reversed DNS name like com.mycompany. here.
If your app is sandboxed there is another limitation that you cannot send an userInfo dictionary.
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
add a comment |
There are dozens of different options of how to achieve this. Each with their own advantages and disadvantages.
Probably the easiest is sending notifications using the DistributedNotificationCenter from Foundation. It’s just like the regular NotificationCenter but across Process-Boundaries.
On the receiving side you register an observer like this:
DistributedNotificationCenter.default().addObserver(forName: NSNotification.Name("com.mycompany.MyNotification"), object: nil, queue: nil) { notification in
print(notification)
}
On the sending side you post a notification like this:
DistributedNotificationCenter.default().post(name: NSNotification.Name("com.mycompany.MyNotification"), object: nil, userInfo: ["data": "to send"])
This is not very secure though - any process can send and receive those notifications. So if they contain private data you shouldn't use this method. This also means you should use a unique notification name. Good idea to start that with a reversed DNS name like com.mycompany. here.
If your app is sandboxed there is another limitation that you cannot send an userInfo dictionary.
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
add a comment |
There are dozens of different options of how to achieve this. Each with their own advantages and disadvantages.
Probably the easiest is sending notifications using the DistributedNotificationCenter from Foundation. It’s just like the regular NotificationCenter but across Process-Boundaries.
On the receiving side you register an observer like this:
DistributedNotificationCenter.default().addObserver(forName: NSNotification.Name("com.mycompany.MyNotification"), object: nil, queue: nil) { notification in
print(notification)
}
On the sending side you post a notification like this:
DistributedNotificationCenter.default().post(name: NSNotification.Name("com.mycompany.MyNotification"), object: nil, userInfo: ["data": "to send"])
This is not very secure though - any process can send and receive those notifications. So if they contain private data you shouldn't use this method. This also means you should use a unique notification name. Good idea to start that with a reversed DNS name like com.mycompany. here.
If your app is sandboxed there is another limitation that you cannot send an userInfo dictionary.
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
There are dozens of different options of how to achieve this. Each with their own advantages and disadvantages.
Probably the easiest is sending notifications using the DistributedNotificationCenter from Foundation. It’s just like the regular NotificationCenter but across Process-Boundaries.
On the receiving side you register an observer like this:
DistributedNotificationCenter.default().addObserver(forName: NSNotification.Name("com.mycompany.MyNotification"), object: nil, queue: nil) { notification in
print(notification)
}
On the sending side you post a notification like this:
DistributedNotificationCenter.default().post(name: NSNotification.Name("com.mycompany.MyNotification"), object: nil, userInfo: ["data": "to send"])
This is not very secure though - any process can send and receive those notifications. So if they contain private data you shouldn't use this method. This also means you should use a unique notification name. Good idea to start that with a reversed DNS name like com.mycompany. here.
If your app is sandboxed there is another limitation that you cannot send an userInfo dictionary.
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
answered Nov 23 '18 at 17:40
SvenSven
20.4k44568
20.4k44568
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
add a comment |
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
Great, I will test it.. the message does not include private data, it is only a message to the menu app to reload data from persistent storage... Thank you for answering my question.. The app is not sandboxed (github.com/rsyncOSX/RsyncOSX)
– Tevensen
Nov 23 '18 at 18:54
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450639%2fintercommunication-between-to-macos-apps-on-local-mac%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
