Comment 7 for bug 897469

I haven't been able to resolve the issue with refreshing yet. It would probably take someone familiar with the rendering code very little time to find out what's going on.

There's also one more thing. As it is now, the code uses a process id to know whether simple-scan is running and whether it should recover any pages. There could be problems if one uses two instances on two different computers sharing a home directory (via nfs, say). Then one instance will try to take ownership of the pages of the other. A possible solution would involve making simple-scan unique (using GtkApplication) and then using some sort of (dbus?) session id to tag the autosaves, instead of just the process id.

On the other hand, one could argue that even if two machines share the same home directory, they should have a local .cache directory. Then the problem disappears entirely.

I haven't researched this yet, and perhaps it is not the use case we are aiming for.