ADOR Caching

One of the most powerful features of XMPie's patented dynamic print technology is the ability to cache objects in the output stream so that reusable objects are placed into the output file only once and are referenced for all additional records/recipients that use the same object. This means that the print file is created faster, is smaller in size, can be sent to the printer faster and processes faster on the printer or RIP.

XMPie makes the decision which objects are cached automatically, based on the ADOR type. Usually, Graphic and Text file ADORs are reusable objects, and are thus cached. Text ADORs, on the other hand, are usually unique and will not be cached. However, occasionally, it may be desirable to change this automatic behavior for certain ADORs.

Important! It is recommended that you change this automatic behavior only if you fully understand the caching mechanism, and the impact of the change.

InDesign objects

XMPie treats objects in the InDesign document in one of three ways:

  • Fixed: When the object contains no ADORs.

  • Reusable: When the object contains a file-based ADOR, such as a Graphic ADOR or a Text File ADOR.

  • Unique: When the object contains any other type of ADOR, such as a Text ADOR.

An "object" in InDesign is a text frame or a graphic frame.

How are reusable objects used?

Records/recipients to be processed are checked to see if the same Graphic or Text File ADORs contain a file that is used for more than one record/recipient in the database being processed. Reusable object information is stored in memory as the production job is processed. This process is designed to work where Graphic or Text File ADORs contain a file that is used for more than one record/recipient.

In some unusual circumstances, it is possible for a Graphic or Text File ADOR to call an asset which is unique for every record or recipient in the database, for example a personal photo of each recipient. In this case, storing the InDesign object in memory serves no purpose and for particularly large databases, and large asset sizes, can lead to excessive memory use.

If your Graphic or Text File ADOR will be unique for every record/recipient in the database, then you can disable the caching mechanism by renaming the ADOR to include .unique at the end of the ADOR name. For example, a Graphic ADOR named "photo" can be renamed "photo.unique" to disable the caching mechanism.

Risks of disabling the caching on an ADOR

If you add .unique to the name of a Graphic or Text File ADOR which contains an asset that is used by multiple records/recipients in the database, then the InDesign object will not be cached and the object will be added to the output file for each record/recipient. This means that the print production will be slower and create a significantly larger print file than needed.

How are Unique objects used?

Unique objects are inserted directly into the output file for each record/recipient processed and are not cached. For example, an InDesign text frame that contains the body of a letter with static text as well as some Text ADOR, is considered unique since the chance of another record/recipient with the exact same values in each Text ADOR used in the text frame, is very low.

In some occasions, it is possible for a Text ADOR to contain a value which is reusable by some records/recipients in the database. For example, a Text ADOR "club level" could contain the values "Gold", "Silver" or "Bronze", where many recipients will use one of these values. If this Text ADOR is used in a text frame in InDesign either by itself, or with only static text (meaning that the text frame does not contain other unique ADORs) then it is possible to enable the caching mechanism by adding .reusable at the end of the ADOR name. For example, "club level" can be renamed "club level.reusable" to enable the caching mechanism.

Risks of enabling the caching on an ADOR

If you add .reusable to the name of an ADOR, then InDesign objects that use that ADOR will be cached and stored in memory to check for other records using that InDesign object with the same ADOR value. This means that more objects will be stored in memory, and for large databases, if used incorrectly, this increases the risk that the available memory may not be sufficient to complete the entire production job.