Re: Launchd daemon / user app communication
Re: Launchd daemon / user app communication
- Subject: Re: Launchd daemon / user app communication
- From: Erwin Namal <email@hidden>
- Date: Wed, 01 May 2013 11:52:06 +0200
Thank you for your reply.
I checked out distributed objects after posting my message, and thought I could make it work in the direction user application (proxy) → daemon (real object), I couldn't make it work in reverse. So I was left with the only possibility: polling the daemon for logs instead of waiting for them.
The scheme I used is contact a distant object owned by the daemon (works) to tell it to call me back at an address for logging purposes. Thought the launchd system-wide daemon had the address, it was unable to establish a connection. Is there a reason for that?
-E
On 1 mai 2013, at 05:16, Damien Sorresso <email@hidden> wrote:
> On Apr 29, 2013, at 11:20 AM, Jens Alfke <email@hidden> wrote:
>> On Apr 29, 2013, at 10:16 AM, Rustam Muginov <email@hidden> wrote:
>>
>>> The simplest Objective-C way to communicate would be distributed objects.
>>> It is not, of cause, the most secure way - but definitely the simpliest one.
>>
>> XPC is based on DO
>
> No, it isn't.
> --
> Damien Sorresso
> email@hidden
>
>> but has additional security features (e.g. for data validation) to make it safe to use between mutually-untrusted processes.
>> (Again, this is my understanding from reading overview docs. I haven't used it myself.)
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Darwin-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden