Shared memory in OS X?

[Mike H.]

I am porting an app from Classic to OS X...and the biggest problem I've run
into is how to get live notification of changes to prefs.

The app consists of a "daemon" and a preference-setter. The daemon is
Mach-O, the preference-setter is written in Carbon.

Right now, I just have the daemon continuously polling a file, which is not
the best way to do it. Is there anyway for a Carbon app to instantly
communicate with a Mach-O app? I'd prefer to avoid AppleEvents...

Thanks!

Mike Hunson

[Frederick Cheung]

On Mon, 29 Sep 2003, Mike H. wrote:

> I am porting an app from Classic to OS X...and the biggest problem I've run
> into is how to get live notification of changes to prefs.
>
> The app consists of a "daemon" and a preference-setter. The daemon is
> Mach-O, the preference-setter is written in Carbon.
>
> Right now, I just have the daemon continuously
>polling a file, which is not
> the best way to do it. Is there anyway for a Carbon app to instantly
> communicate with a Mach-O app? I'd prefer to avoid AppleEvents...

For actual shared memory, there's always shmctl and friends, but for what
you are trying to do CFMessagePort is probably more appropriate
Or you could just send the daemon a signal telling it to reread its
configuration file
Why are you so hesitant to use apple events?

Fred

>
> Thanks!
>
> Mike Hunson
>
>

[Paul Mitchum]

Mike H. <nospam@endspam.org> wrote:

> I am porting an app from Classic to OS X...and the biggest problem I've run
> into is how to get live notification of changes to prefs.
>
> The app consists of a "daemon" and a preference-setter. The daemon is
> Mach-O, the preference-setter is written in Carbon.
>
> Right now, I just have the daemon continuously polling a file, which is not
> the best way to do it. Is there anyway for a Carbon app to instantly
> communicate with a Mach-O app? I'd prefer to avoid AppleEvents...

Have a look-see: <http://makeashorterlink.com/?F5A413C06>

Your best bet looks to be a Core Foundation distributed notification. A
less Apple-oriented solution would be pipes or sockets, but those would
still require polling the filesystem.

[Eric Albert]

In article <1g21w8l.16i6e0qzjuo6hN%usenet@mile23.com.r3m0v3 >,
[email]usenet@mile23.com[/email].r3m0v3 (Paul Mitchum) wrote:

> Mike H. <nospam@endspam.org> wrote:
>

> > I am porting an app from Classic to OS X...and the biggest problem I've run
> > into is how to get live notification of changes to prefs.
> >
> > The app consists of a "daemon" and a preference-setter. The daemon is
> > Mach-O, the preference-setter is written in Carbon.
> >
> > Right now, I just have the daemon continuously polling a file, which is not
> > the best way to do it. Is there anyway for a Carbon app to instantly
> > communicate with a Mach-O app? I'd prefer to avoid AppleEvents...

>
> Have a look-see: <http://makeashorterlink.com/?F5A413C06>
>
> Your best bet looks to be a Core Foundation distributed notification. A
> less Apple-oriented solution would be pipes or sockets, but those would
> still require polling the filesystem.

I'll second Paul's suggestion. CFNotifications are the standard way to
do this.

-Eric

--
Eric Albert [email]ejalbert@stanford.edu[/email]
[url]http://rescomp.stanford.edu/~ejalbert/[/url]