Re: Even more DO problems
Re: Even more DO problems
- Subject: Re: Even more DO problems
- From: Sailor Quasar <email@hidden>
- Date: Tue, 10 Jun 2003 01:52:37 -0400
On Tuesday, June 10, 2003, at 01:36 AM, Lloyd Dupont wrote:
not sure if these ideas will help any. but...
1. Could it be that you haven't set up the sendport on the server
correctly?
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.
2. Then you also have to think about your argument (NSData *)data. Is
it going to also be a proxy object on the server to the client-owned
data object ? So any calls on the server (eg [data doSomething] )may
occur on the client side.
I pass it as (bycopy NSData *). Sorry, forgot to mention that before. I
specifically don't want the data object proxied.
3. you can get more control of the DO stuff if you look at the
NSConnection delegates like
- (BOOL)connection:(NSConnection *)conn
handleRequest:(NSDistantObjectRequest *)doReq
I already use an NSConnection delegate, but I didn't know that that
method could be used. How would it help, frankly?
-- Sailor Quasar, just another player in The World
"Come with me in the twilight of the summer night for awhile"
Email: email@hidden
_______________________________________________
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.