Re: Even more DO problems
Re: Even more DO problems
- Subject: Re: Even more DO problems
- From: Joji Mori <email@hidden>
- Date: Tue, 10 Jun 2003 20:38:16 +1000
Hey, one thing I'm pretty sure you have to make sure you aren't doing
is autoreleasing the client connection, if I remember correctly, the
connection has to remain until the end of the proxy object. What are
you using to create the NSConnection on the client side?
In regards to your responses... Yeah, I think you might know a bit more
about DO than me anyway
Also, there have been issues in the past with using bycopy for custom
classes (ie you have to override a certain method to get it working
properly) but this wont affect you since you are using NSData.
You can confirm that by calling NSObject's isProxy on data just to
confirm anyway
The delegates, yeah, I can't see how this would directly help with your
problem, I just mentioned them because you said we can't see the
internal workings of DO.. And I guess these delegates are the only
things we do get access to
Joji
Sailor Quasar said...
I don't set up the send port for the server. I only set up a receive
port and rely on the documented semantics of NSConnection for it to set
up the send port for the well-known server connection. The child
conections are supposed to use the same port semantics, as I understand
it.
I pass it as (bycopy NSData *). Sorry, forgot to mention that before. I
specifically don't want the data object proxied.
I already use an NSConnection delegate, but I didn't know that that
method could be used. How would it help, frankly?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.