Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

Limiting pre-cache for slow networks


  • After upgrading one of our systems that is running on a cellular modem from 3.5 to 3.7 we have had some issues on the initial connection due to the pre-caching in the serviceWorker. Eventually several things will usually time out and some of our users are unable to load the site due to the number of requests and data transfer .

    Our UI does not need many of the pre-cached items, so I have tested using a custom pre-cache manifest. I have tested both an empty manifest, and a manifest with our UI's custom modules and content.

    So far in testing I have not noticed any issues, and the initial page load is nearly 1/6 the size it was before.

    Are there any foreseeable issues with using a custom pre-cache manifest, or are there Mango or vendor modules that may not be obvious but should likely be pre-cached?