Wed Nov 30 10:05:07 EST 2016

migration: treating machine state as cache

I've been thinking about migration, and it is quite hard to implement
properly.  what seems simpler is to migrate only the meaningful
application state, and treat all the rest of the state (which is
usually *much* larger) as cache.

This is what android does[1]: save only the significant portion of the
application state, and allow the OS to simply kill the application
state when it is swapped out.

This idea can be pushed very far.

[1] https://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle