~
Docs
CoursesLanguageSystemUserspaceToolsManualGlossary
AgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAxesAxisAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClamClayCold atomCometCommitConsContextCordCoreCueDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHeadHelmHoodHoonInvite TreeIrisJaelJamJetKelvin versioningKernelKeyfileKeywordsKhanKilnLandscapeLarkLegLickListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented ProgrammingSubjectSubscriptionTailTapeTermThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
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.
~Urbit Docs
HomeCoursesLanguageSystemUserspaceToolsManualGlossary
GitHubAirlock APIsUrbit BinariesDeveloper Mailing ListIssue TrackerWhitepaper
Privacy Policy
Terms of Service
[email protected]