(In reply to comment #74)
> We could litter our code with O_NONBLOCK/WOULDBLOCK checks, but that is neither
> easy nor nice.
You knew the job was dangerous when you took it, Fred. :-)
> I don't know of other applications that store profile-like data
> as frequently as we do (browsing history), and manage to not interfere with
> other instances. If you can point us at some, we might be able to adapt their
> techniques.
I'm not sure how KDE's konqueror browser handles this situation, but it does seem to handle multiple instances running on different machines pretty well. It might be worth checking out.
(In reply to comment #74) WOULDBLOCK checks, but that is neither
> We could litter our code with O_NONBLOCK/
> easy nor nice.
You knew the job was dangerous when you took it, Fred. :-)
> I don't know of other applications that store profile-like data
> as frequently as we do (browsing history), and manage to not interfere with
> other instances. If you can point us at some, we might be able to adapt their
> techniques.
I'm not sure how KDE's konqueror browser handles this situation, but it does seem to handle multiple instances running on different machines pretty well. It might be worth checking out.