On Nov 2, 2009, at 10:04 PM, Jens Alfke wrote:
> This misfeature has confused a lot of people over the years, including me. My
> solution, once I found out what was going on, was to never send NSURLs over
> DO — I converted them to NSStrings on the sending side and back to NSURLs on
> the rece
On Nov 2, 2009, at 9:36 PM, aaron smith wrote:
There seems to be some kind of bug when passing around an NSURL
through
distributed objects.
Oh, you've run into _that_! :-/
For some reason, NSURLs are unexpectedly not copied when sent over DO,
the way other "value" objects like NSStrings
OK. I figured it out. Here's the answer just in case anyone else runs into
this.
There seems to be some kind of bug when passing around an NSURL through
distributed objects. You need to make sure to make a new NSURL object in the
"server" applications' code.
like this:
- (void) openWithGity:(NSU
hey Folks, quick question.
I'm building an app that I'm providing a command line tool for. I have it
hooked up and working. However the strange thing is that it works the first
time it's run, but then just throws exceptions.
I'm using a proxy object, which is exposed through NSConnection, and thr
