Page Summary
-
Container.Callbackprovides clients with a way to be notified about container refresh events. -
Clients implementing this interface will receive callbacks indicating the start, success, or failure of a container refresh.
-
containerRefreshBeginis always called beforecontainerRefreshSuccessorcontainerRefreshFailurefor a given refresh type. -
While
containerRefreshBeginis guaranteed to be called before the corresponding success or failure callback, no other ordering guarantees are provided for refresh events.
Callback will be invoked after the resource has been successfully loaded. A client may implement this interface to receive information when the contents of the container have been refreshed.
You may rely on the fact that containerRefreshBegin(Container, Container.RefreshType) will be called for a given
Container.RefreshType before its associated containerRefreshSuccess(Container, Container.RefreshType) or containerRefreshFailure(Container, Container.RefreshType, Container.RefreshFailure). However, do not make any other assumptions about ordering. In
particular, there may be two refreshes outstanding at once (both SAVED and NETWORK) or a SAVED refresh may occur before a NETWORK refresh.
Public Method Summary
| abstract void | |
| abstract void |
containerRefreshFailure(Container container, Container.RefreshType refreshType, Container.RefreshFailure refreshFailure)
|
| abstract void |
Public Methods
public abstract void containerRefreshBegin (Container container, Container.RefreshType refreshType)
Called when a refresh is about to begin for the given refresh type.
public abstract void containerRefreshFailure (Container container, Container.RefreshType refreshType, Container.RefreshFailure refreshFailure)
Called when a refresh failed for the given refresh type.
public abstract void containerRefreshSuccess (Container container, Container.RefreshType refreshType)
Called when a successful refresh occurred for the given refresh type.