Comment Comment by aboodman Yeah, it's a big part of the tradeoff for this kind of architecture. In Zero, this is a first-class concern via the ConnectionStatus API:https://zero.rocicorp.dev/docs/connectionErrors and connection are handled in a centralized place so that they automatically get applied to all paths.Errors immediately disconnect the app and trigger UI. Writes are no longer accepted. After 1 minute of of failed connection attempts, same happens.This formalizes and enforces the common pattern in popular sync-based apps of detecting disconnects fairly aggressively and warning the user. parent aboodman 4 months ago
https://zero.rocicorp.dev/docs/connection
Errors and connection are handled in a centralized place so that they automatically get applied to all paths.
Errors immediately disconnect the app and trigger UI. Writes are no longer accepted. After 1 minute of of failed connection attempts, same happens.
This formalizes and enforces the common pattern in popular sync-based apps of detecting disconnects fairly aggressively and warning the user.