RESTCache - Overview

Go to List

Mobile

5.0

(2 ratings)

0 reviews

Adrian

Created on 15 June 2017

Details

Client and server side cache for use with REST APIs. API throttling allows reducing the number of REST calls when data does not change very often.

What’s new (4.0.0)

small improvements

Reviews (0)

Tags

cache

throttling

REST

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 Adrian who created this component.

Dependencies

RESTCache has no dependencies.

Requirements

Platform:

11.0.0.200

Database:

All

Stack:

All

Team

Component Consumers

Weekly Downloads

Related Components

A fully responsive and beautiful UI framework that works within the OutSystems Platform. Build amazing looking applications, in a fraction of the time, which work perfectly across devices. Learn how to start using Silk UI and see the examples at silkui.outsystems.com . Obtain assistance on using Silk UI in our forums .

33534

Create amazing applications using this fully integrated UI framework for OutSystems, with dozens of UI patterns ready to use.

14833

Allow you to upload multiple files in one upload form or using drag and drop functionality.

3456

More from Adrian

This application provides a simple yet aggressive removal of the massive amounts of useless data on your Cloud Personal Environment. It may work on non cloud environments but has not been tested outside a Cloud Personal Environment. I used LogsManagement and DBCleaner for inspiration, many thanks to Carlos Alfaro the author of LogsManagement (http://www.outsystems.com/forge/component/1195/logs-management/) and to Acácio Porta Nova the author of DBCleaner (http://www.outsystems.com/forge/423/)

625

An Enterprise Glossary Application with Specifications Management capabilities, advanced import/export capabilities and synchronization to/from Enterprise Architect and JIRA.

A mobile app with offline cache using REST services. Local app cache is used when: - there is no connection to the server; - there is an error retrieving information from the server; Server-side cache is used when: - there is a timeout retrieving information via REST - there is an error retrieving information via REST - call throttling dictates cache should be used instead of the REST api. Server cache throttling allows one call every 15 seconds. Example on how to send error codes via REST and handle REST errors.