restarts

When the server auto-restarts at some point, the offline data will sync back up and resolve any conflicts.

Every generation starts at 1, and every time it restarts, you read the current generation and increment it?

Given the triple {ID, Generation, Node}, is the Node id unique & different across restarts or the same?

It isn't even unique if a node restarts, but it is unique over a system instances lifetime.

That's true; however Chrome restarts in a couple of seconds and restores most of your state.

Prior to Enterprise2 upgrades are done with a package that updates the appliance 'in-place' and restarts services (or a reboot?

Those generating ROP gadgets would have to wait till the application restarts to try again.

There's no immediate user feedback, resulting in multiple clicking, which restarts the page load.

It's still worth running for no other reason than reducing the overall resources my browser uses and extending the time required between restarts.

For example, let's say I am using redis and I want to ensure it always restarts (for whatever reason).

How does that work with nginx or haproxy, which support zero-downtime restarts?

Both are prone to random restarts and lags and other issues.

> daemontools will just keep restarting your process as fast as possible, taking 100% CPU if possible supervise [2]: "It restarts./run if./run exits.

Yep, machine/compose/swarm are great tools from Docker and I'm already using it, but compose is more of a "dev" tool so it restarts all containers with every new deploy.

I would say that coming from any language where this is limited to the "try...catch" paradigm, seeing the separation and possibility provided by restarts is absolutely a mind blowing experience.

What 8.1 does currently is says, "Windows is restarting in 1 day", then 1 day later if you haven't restarted (for a lot of people, that's plausible) it restarts for you, regardless if what you're doing.