Local Content Provider

Stable Version 1.0.15 (OutSystems 11)
Published on 6 Nov (4 weeks ago) by 
Created on 19 Oct

Local Content Provider

This component makes caching binary files locally on the device possible, which will be available for all apps on the device.
Read More

The main goal of this component is to reduce unnecessary network traffic!

Binary responses can be cached as a file in the device, which will be there for a configurable amount of days with a site property. The location of the file is also stored in the local storage which will be synced to a server entity together with a unique device id. The benefit of storing it this way is that the content can be used by multiple apps (just local entities does not have this option).

Please don't hesitate to contact me if you have improvement ideas or other questions!

A demo is still being worked on and will be available shortly!

What’s new (1.0.15)
  • In case of expired file, the binary will be returned. The result code will let the consumer know if it was expired, and so, if the file is deleted after that request.
  • As noted in the previous point; expired files will be deleted. From now on this happens asynchronously.
  • Logging for this component can be turned on/off with a Site Property (this will be synced with a local Client Variable in the SyncClientVariables action)
Reviews (2)
26 Oct
in version 1.0.8
Works like a charm!
23 Oct
in version 1.0.8
works perfectly fine!
Support Options
This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from Jobbe Maas who created this component.
See all 2 dependencies
Component Consumers
No consumers yet.
Weekly Downloads