* Does it make sense to cache transforms in my application?
If you mean caching pixels in a transform, no. There is a one-pixel cache already implemented. If you mean caching yet existing color transforms... hard to say. A transform can take a lot of memory. Creating a transform is a matter of 0.5 seconds on most machines. If you are going to use a lot of simultaneous transforms, maybe. But this is going to make thinks complex. I would first try the easier, non-caching way. If this gives a sluggish feeling to the app, then try caching.
Presumably the cache is stored in memory. Is there a possibility of placing the cache in a memory-mapped file so that obtaining access to the cached transform is as easy as memory-mapping the existing file? This way the transform can be removed from memory when it is not needed and only consume disk space.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Lcms-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/lcms-user
