Re: NSConnection registerName limitations?
Re: NSConnection registerName limitations?
- Subject: Re: NSConnection registerName limitations?
- From: Chris Kane <email@hidden>
- Date: Sat, 20 Dec 2003 14:29:35 -0800
On Dec 12, 2003, at 11:21 AM, Jonathan Wight wrote:
I'm using DO to talk to a helper process and decided to use a UUID (I
thought it would be unique) for the NSConnection's registerName method.
Unfortunately I can't communicate to the helper if I use a UUID. I am
definitely using the same name for the client and the server (helper) -
I establish the name before the DO session via a pipe. If I used a hard
coded string ("HelperProcess") as the registered name then the
communication succeeds. This leads me to believe that a UUID is either
too long of a string to use as a DO registered name or contains illegal
characters (the '-' character perhaps).
So what are the rules to make a legal DO registered name?
DO names are limited to about the first 128 characters of the passed-in
string, by the OS. I don't think there are any particularly illegal
characters, however, except that an embedded \0 will probably cause the
name to be shorter than you expect. :-) DO will convert the string to
UTF8 then truncate to fit the OS's limits, but I've never heard of
cases of characters being illegal. The OS doesn't care what characters
are in the string.
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
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.