In CinePaint is an device link file based caching implemented.
<http://cinepaint.sf.net>
Naturally not all options are available with device links.
Once You use device links, will be bound by them or You have to create
exceptions.
Would an transform cache fit in an global memoy space? This using the
same memory across applications and save space. Is taking the profile id's
of both involved profiles plus creation options sufficent?
regards
Kai-Uwe Behrmann
+ imaging development / panoramas
+ color management
+ email: [EMAIL PROTECTED]
+ CMS proposal <www.behrmann.name>
Am 13.12.04, 10:45 -0500 schrieb Leonard Rosenthol:
> At 10:28 AM 12/13/2004, Bob Friesenhahn wrote:
> >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.
>
> I was discussing a similar implementation recently with a vendor
> of profile building tools. He was saying that they've built DeviceLink
> profiles in the 100's of megs in size - and as such, tools that keep that
> profile in memory can thrash systems. So we were talking about memory
> mapping the profile for just this reason.
>
>
> LDR
>
> ---------------------------------------------------------------------------
> Leonard Rosenthol <mailto:[EMAIL PROTECTED]>
> Chief Technical Officer <http://www.pdfsages.com>
> PDF Sages, Inc. 215-938-7080 (voice)
> 215-938-0880 (fax)
>
>
-------------------------------------------------------
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
