~
Docs
LanguageCoursesUserspaceSystemToolsManualGuidesOverviewReference
GlossaryAgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClayCold atomCometCommitConsContextCordCoreDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHelmHoodHoonInvite TreeIrisJaelJetKelvin versioningKelvin versioningKeyfileKeywordsKhanKilnLandscapeLegListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented Progr...SubjectSubscriptionTapeThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
Additional
Reference/Glossary/Replay

Replay

Replay is how Vere computes the state of a ship's Arvo instance from the event log after a ship reboots. In order to avoid replaying the entire event log, Replay takes a snapshot of the current state of the ship approximately once every ten minutes. Then when a ship reboots, Replay loads the most recent snapshot and replays events from the event log up to the most recent event.

Further Reading

  • The Vere tutorial: An in-depth technical guide to Vere.
Edit this page on GitHub

Last modified October 8, 2023

~Urbit
HomeGet StartedOverviewEcosystemGrantsEventsBlog
GitHubAirlock APIsUrbit BinariesDeveloper Mailing ListIssue TrackerWhitepaper
Privacy Policy
Terms of Service
support@urbit.org