Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #36864 All Revisions ] Back to Issue ]
Summary 0036864: Product Image thumbnails should be generated to reduce the consumed bandwidth of the Web POS
Revision 2017-09-15 12:32 by marvintm
Description The Web POS by default stores the product images in the local database, but if the number of products is too great, they cannot fit here. There is another configuration which can be used to prevent this problem which can be set by using the preference "Web POS Product Images from server instead of cache".

When this preference is set, a process called "Generate Product Images" must be used. This process reads all product images in a given assortment, and stores them as separate files. The images are then requested by the Web POS as separate images every time the products are searched or browsed, and also in the Product Information tab.

This works correctly, but currently has two aspects which could be improved:

- The process generates just one image for each product (with maximum width 160 pixels). The size of this image is correct for the Product Information tab, but it's too big for the product thumbnails that are used in the Product SEARCH and BROWSE tabs. Having images this big has proved to consume a very significant amount of network bandwidth on real customers.

- The process always generates every image for every product in the assortment. If the assortment is very big, and only a few products have been added, this is very inefficient.


Therefore, the following two improvements are proposed:
- Apart from the big product image used in the Product Information tab, a new, smaller image, will be generated. This smaller image will be then used in the Product SEARCH and BROWSE components.

- A new check parameter will be added to the Generate Product Image process: "Overwrite all images". If this check is enabled, the process will always generate both images for every single product in any case, overwriting each file if it already exists. If it is not checked, the process will then avoid generating images that already exist, generating only the images that do not exist already.
Revision 2017-09-15 12:31 by marvintm
Description The Web POS by default stores the product images in the local database, but if the number of products is too great, they cannot fit here. There is another configuration which can be used to prevent this problem which can be set by using the preference "Web POS Product Images from server instead of cache".

When this preference is set, a process called "Generate Product Images" must be used. This process reads all product images in a given assortment, and stores them as separate files. The images are then requested by the Web POS as separate images every time the products are searched or browsed, and also in the Product Information tab.

This works correctly, but currently has two aspects which could be improved:

- The process generates just one image (with maximum width 160 pixels). The size of this image is correct for the Product Information tab, but it's too big for the product thumbnails that are used in the Product SEARCH and BROWSE tabs. Having images this big has proved to consume a very significant amount of network bandwidth on real customers.

- The process always generates every image for every product in the assortment. If the assortment is very big, and only a few products have been added, this is very inefficient.


Therefore, the following two improvements are proposed:
- Apart from the big product image used in the Product Information tab, a new, smaller image, will be generated. This smaller image will be then used in the Product SEARCH and BROWSE components.

- A new check parameter will be added to the Generate Product Image process: "Overwrite all images". If this check is enabled, the process will always generate both images for every single product in any case, overwriting each file if it already exists. If it is not checked, the process will then avoid generating images that already exist, generating only the images that do not exist already.
Revision 2017-09-15 12:30 by marvintm
Description The Web POS by default stores the product images in the local database, but if the number of products is too great, they cannot fit here. There is another configuration which can be used to prevent this problem: which can be set by using the preference "Web POS Product Images from server instead of cache".

When this preference is set, a process called "Generate Product Images" must be used. This process reads all product images in a given assortment, and stores them as separate files. The images are then requested by the Web POS as separate images every time the products are searched or browsed, and also in the Product Information tab.

This works correctly, but currently has two aspects which could be improved:

- The process generates just one image (with maximum width 160 pixels). The size of this image is correct for the Product Information tab, but it's too big for the product thumbnails that are used in the Product SEARCH and BROWSE tabs. Having images this big has proved to consume a very significant amount of network bandwidth on real customers.

- The process always generates every image for every product in the assortment. If the assortment is very big, and only a few products have been added, this is very inefficient.


Therefore, the following two improvements are proposed:
- Apart from the big product image used in the Product Information tab, a new, smaller image, will be generated. This smaller image will be then used in the Product SEARCH and BROWSE components.

- A new check parameter will be added to the Generate Product Image process: "Overwrite all images". If this check is enabled, the process will always generate both images for every single product in any case, overwriting each file if it already exists. If it is not checked, the process will then avoid generating images that already exist, generating only the images that do not exist already.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker