Re: Best way to pass large objects between tasks?

2009-04-16 Thread Jean-Daniel Dupas
I don't know about other OS X technologies, but IIRC CFMessagePort is optimized to exchange large amount of data between processes. http://developer.apple.com/documentation/CoreFoundation/Reference/CFMessagePortRef/Reference/reference.html Le 16 avr. 09 à 10:44, Oleg Krupnov a écrit : Thank

Re: Best way to pass large objects between tasks?

2009-04-16 Thread Oleg Krupnov
Thanks, Marcel and Graham. It answers my question. I will now look for ways to optimize data transmission between processes, and I think I have already found one. On Thu, Apr 16, 2009 at 3:10 AM, Marcel Weiher wrote: > > On Apr 12, 2009, at 23:26 , Oleg Krupnov wrote: > >> I haven't tried either

Re: Best way to pass large objects between tasks?

2009-04-15 Thread Marcel Weiher
On Apr 12, 2009, at 23:26 , Oleg Krupnov wrote: I haven't tried either of the methods I mentioned so far (because I'm lazy, sorry:), but what I have tried is I created NSData from the large object by using NSKeyedArchiver. It has taken forever, so that I had to force-quit the process. Yes, NS

Re: Best way to pass large objects between tasks?

2009-04-14 Thread Michael Ash
On Tue, Apr 14, 2009 at 9:23 AM, Karan, Cem (Civ, ARL/CISD) wrote: >> >I haven't tried either of the methods I mentioned so far >> (because I'm >> >lazy, sorry:), but what I have tried is I created NSData >> from the large >> >object by using NSKeyedArchiver. It has taken forever, so >> that I had

Re: Best way to pass large objects between tasks?

2009-04-14 Thread Karan, Cem (Civ, ARL/CISD)
> >I haven't tried either of the methods I mentioned so far > (because I'm > >lazy, sorry:), but what I have tried is I created NSData > from the large > >object by using NSKeyedArchiver. It has taken forever, so > that I had to > >force-quit the process. That's why I am asking if the same th

Re: Best way to pass large objects between tasks?

2009-04-13 Thread Yoshiaki Katayanagi
Oleg Krupnov wrotes >I haven't tried either of the methods I mentioned so far (because I'm >lazy, sorry:), but what I have tried is I created NSData from the >large object by using NSKeyedArchiver. It has taken forever, so that I >had to force-quit the process. That's why I am asking if the same

Re: Best way to pass large objects between tasks?

2009-04-13 Thread Michael Ash
On Mon, Apr 13, 2009 at 2:09 AM, Oleg Krupnov wrote: > I need to pass objects from one task (child) to another (parent) on > the same machine. > > Currently I am considering two alternatives: Pipes vs Distributed > Objects, and my main concern is performance, because the object is > really large.

Re: Best way to pass large objects between tasks?

2009-04-12 Thread Graham Cox
On 13/04/2009, at 4:26 PM, Oleg Krupnov wrote: what I have tried is I created NSData from the large object by using NSKeyedArchiver. It has taken forever, so that I had to force-quit the process. Well, maybe you should concentrate on fixing this. It's hard to see what could be taking so mu

Re: Best way to pass large objects between tasks?

2009-04-12 Thread Oleg Krupnov
Thanks Graham. I haven't tried either of the methods I mentioned so far (because I'm lazy, sorry:), but what I have tried is I created NSData from the large object by using NSKeyedArchiver. It has taken forever, so that I had to force-quit the process. That's why I am asking if the same thing is g

Re: Best way to pass large objects between tasks?

2009-04-12 Thread Graham Cox
On 13/04/2009, at 4:09 PM, Oleg Krupnov wrote: I need to pass objects from one task (child) to another (parent) on the same machine. Currently I am considering two alternatives: Pipes vs Distributed Objects, and my main concern is performance, because the object is really large. How large is

Best way to pass large objects between tasks?

2009-04-12 Thread Oleg Krupnov
I need to pass objects from one task (child) to another (parent) on the same machine. Currently I am considering two alternatives: Pipes vs Distributed Objects, and my main concern is performance, because the object is really large. With pipes, I need to serialize (archive) the object into NSData