Path: ...!news.iecc.com!.POSTED.news.iecc.com!not-for-mail From: John Levine Newsgroups: comp.arch Subject: Re: Continuations Date: Mon, 15 Jul 2024 19:43:34 -0000 (UTC) Organization: Taughannock Networks Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 15 Jul 2024 19:43:34 -0000 (UTC) Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="68108"; mail-complaints-to="abuse@iecc.com" In-Reply-To: Cleverness: some X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: johnl@iecc.com (John Levine) Bytes: 1727 Lines: 15 According to EricP : >> Airline reservation and credit card systems still work this way, and >> have amazing transaction rates, like 1000 updates/sec to an individual >> database record. > >In a classic state machine there is a loop around a CASE statement >based on the current state number. The last thing each state case >does is assign the next state number to jump to. Right. This is what we'd now call an event loop, with code dispatched in response to external events like I/O completion. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly