fix: caching mechanism #65

New Issue

sudharshan · 2019-07-27T14:38:20+08:00

sudharshan commented

2019-07-27 14:38:20 +08:00

The currently applied request level caching mechanism still has load times, when accessing pages like ConversationPage and ContactPage.

The mechanism needs to be capable of storing state of the last request and returning it instantly, even in the presence of an Internet connection.

The currently applied request level caching mechanism still has load times, when accessing pages like ConversationPage and ContactPage. The mechanism needs to be capable of storing state of the last request and returning it instantly, even in the presence of an Internet connection.

sudharshan added the

bug

help wanted

logic

labels 2019-07-27 14:38:20 +08:00

sudharshan commented

2019-07-27 22:08:45 +08:00

Poster

So, a possible strategy for the caching, instead of returning the cache only on a network error, each cache-able api_provider returns a stream, which first returns the cache and then optionally returns the network request if available after which the stream is closed

Then when the calls are made, the streams should be handled appropriately, either with StreamBuilders or any other way.

So, a possible strategy for the caching, instead of returning the cache only on a network error, each cache-able api_provider returns a stream, which first returns the cache and then optionally returns the network request if available after which the stream is closed Then when the calls are made, the streams should be handled appropriately, either with StreamBuilders or any other way.

sudharshan self-assigned this 2019-07-27 22:08:51 +08:00

sudharshan added this to the v0.1 milestone 2019-09-23 22:05:10 +08:00

Sign in to join this conversation.