On Dec 20, 2009, at 10:46 AM, Evan Schoenberg, M.D. wrote: > > On Dec 17, 2009, at 11:10 AM, EdLagache wrote: > >> 1815 -[NSSocketPort >> _handleMessage:from:socket:] >> 1815 -[NSConcretePortCoder >> dispatch] >> 1815 -[NSConnection >> handlePortCoder:] >> 1815 -[NSConnection >> handleRequest:sequence:] >> 1815 _NSWalkData2 >> 1815 -[NSConcretePortCoder >> decodeRetainedObject] >> 1815 - >> [NSConcretePortCoder decodeInvocation] >> 1815 _NSWalkData2 >> 1815 - >> [NSConcretePortCoder decodeRetainedObject] >> 1815 -[NSDictionary >> (NSDictionary) initWithCoder:] >> 1815 >> _NSWalkData2 >> 1815 - >> [NSConcretePortCoder decodeRetainedObject] >> 1815 - >> [NSImage initWithCoder:] >> 1815 - >> [NSImage _newRepresentation:] >> 1815 - >> [NSProxy isKindOfClass:] >> 1815 >> _CF_forwarding_prep_0 >> 1815 >> ___forwarding___ >> >> 1815 -[NSDistantObject methodSignatureForSelector:] >> >> 1815 -[NSConnection sendInvocation:internal:] >> >> 1815 CFRunLoopRunInMode >> >> 1815 CFRunLoopRunSpecific >> >> 1815 mach_msg >> >> 1815 mach_msg_trap > > This sample of decoding an image's representation seems to show that > the other side has received an NSDistantObject - that is, the > object's data is still on the sending side - and is trying to > request it. I'm not sure why this behavior would be different for > Applescript, but I suspect that if we wanted to try to fix this in > the existing code base we might want to convert to raw NSData and > then from there to a fresh NSImage any image brought in via > Applescript. > > Since the new network code will be using a raw data stream to > communicate images, this should become a nonissue.
Ya, let's focus on the new stuff and not worry about the existing networking. Chris -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
