On Aug 13, 2008, at 9:09 PM, Michael B Johnson wrote:
What if the ImageIO folks architected their stuff like the QTKit
folks did, where there was a specific, restricted API that worked
from 64-bit regardless. In their case, they have a separate 32 bit
server process that talks to the 64 bit process via completely
opaque handles (i.e. QTMovie pointers) and there's a clear
demarcation. I use this very successfully every day (just the other
day I had a 64 bit app with a VSIZE of 125GB making thousands of
QTMovie objects from many, many threads, all happily running on
10.5.4).
The main problem with maintaining a single 32-bit process for
compatibility is that when the majority of your applications are 64-
bit, you are incurring a significant memory penalty for loading
additional frameworks that are only being used by that process.
Granted, we aren't at that point today, but given the topic it seems
like quite a few people are working towards it :)
--
David Duncan
Apple DTS Animation and Printing
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
