jonasz
commented
4 years ago Catalog management indeed seems like an open issue in Turtledove in general. I think it strongly depends on the frequency of bundle refreshes - which, as I understand, has not been established yet.
We suggest that there should be an indicator of product availability in the product bundle.
This sounds very useful. The current price and the presence of promotions could also be included in the bundle.
It seems that frequent product bundle refreshes will be needed in TURTLEDOVE, which might have a negative impact on users' bandwidth. Could you please explicit the mechanism you envision for the product bundle refresh?
In general, the product-level approach to Turtledove enables some improvements compared to vanilla Turtledove:
- In vanilla TD, the browser would have to update each creative bundle separately, without knowing that the bundles may overlap in terms of products. (See e.g. Andrew's description of potential interest groups here: https://github.com/WICG/turtledove/issues/36#issuecomment-648970979). With product-level focus, the updates may happen for each product just once.
- In addition to that, the browsers could seek optimizations by caching heavier product assets and not fetching them if not necessary. ("Tell me the price and availability for product X, and only return the thumbnail if it changed recently.")
How to handle Advertising Use Cases linked to Catalog Management (cf https://github.com/w3c/web-advertising/blob/master/support_for_advertising_use_cases.md#catalog)?
The use cases include product availability management, product price management, product promotion management.
We suggest that there should be an indicator of product availability in the product bundle.
It seems that frequent product bundle refreshes will be needed in TURTLEDOVE, which might have a negative impact on users' bandwidth. Could you please explicit the mechanism you envision for the product bundle refresh?