Skip to content
pCon.configurator onlineDocumentation
Esc
↑↓navigate↵open⌘Jpreview
On this page

Differences Between Online Configurator and pCon.basket

The handling of generated article images differs between Online Configurator and pCon.basket.

The client of the Online Configurator generates an article image invoking the getGeneratedImage operation (§getGeneratedImage) for a particular article item, specifying (implicitly or explicitly) the desired rendering and camera settings as well as a tag. The Online Configurator computes an image identifier based on the current configuration of the article item and the specified settings. It then asks the global file cache (§Global File Cache) whether it contains an image matching this identifier. If so, the image is used. Otherwise, an image is generated and stored in the cache. In either case, the article item stores a reference to the image under the tag specified by the getGeneratedImage operation. Consequently, there may be multiple images per article item, and different article items representing the same article configuration may reference different images, even under the same tag.

pCon.basket, on the other hand, maintains a per-project mapping from article configurations to generated article images. Whenever a generated image is needed for a particular article item, the article’s current configuration is looked up in this mapping, and if found, the referenced image is used as the generated article image for this item. If not found, an image is generated using user defined global rendering and camera settings, the image is stored in the global mapping, and used as the generated article image for the item. Consequently, there is only one generated image per article item, generated on demand, and all article items containing the same configuration of the same article share the same image.

For compatibility with pCon.basket, the Online Configurator also supports the per-project mapping from article configurations to article images. Images stored in this mapping shall be called PBK images. The mapping is updated by the getGeneratedImage operation whenever an image is generated using the default tag. The mapping as well as the images referenced by the mapping are stored by the saveSession operation (§saveSession) of the session web service, and restored by the loadSession operation (§loadSession). A position’s PBK image, if known, is returned by the getImages operation (§getImages) using an empty string as tag.

Other than pCon.basket, the saveSession operation of the Online Configurator’s session web service does not attempt to generate any missing PBK images.