Re: NSConnection not working between processes
Re: NSConnection not working between processes
- Subject: Re: NSConnection not working between processes
- From: James Bucanek <email@hidden>
- Date: Fri, 24 Jun 2005 10:58:07 -0700
Aurélien Hugelé wrote on Friday, June 24, 2005:
>you have to use a common DO design here : use your "only half
>NSConnection" to register the client to the server :
>
>the once the client "knows" the server, it just call something like :
>
>[serverProxy registerClient:self];
>
>the server implements this method :
>-(BOOL)registerClient:(id)aClient
>
>then the server retains the passed client, and can message it,
>asynchronously !
>
>it works like a charm...
It does! I guess I had simply assumed that an NSConnection that was using a single NSPort couldn't do full, bidirectional, asynchronous communications. Makes you wonder why we have to create two NSPorts when communicating between threads.
Anyway, it works and that's the important part. It messed up my object design a tad (I really didn't intend for the proxied object to have knowledge about the client's object) but I can live with that.
Thanks so much for the help. You saved me an incident with developer services. ;)
Cheers,
James
--
James Bucanek <mailto:email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden