Optionally execute Callback Behavior on Re-construction after Expiry

On page re-construction after expiry, it might be desired to have the callback behavior of the page executed.

I acknowledge that there is a worst case scenario where callback behavior could hit an invalid component state.

However that worst case scenario should not result in a penalty for the majority of cases where this situation cannot occur.

I am suggesting that behavoir is executed after expiry if the page source specifies it e.g. via an overridable method callBackAfterExpiry().