From cd44be9d3a314492ecc72ce793267aa48c2e88b4 Mon Sep 17 00:00:00 2001 From: Claudio Sacerdoti Coen Date: Thu, 29 May 2003 17:59:37 +0000 Subject: [PATCH] ... --- .../calculemus-2003/hbugs-calculemus-2003.tex | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/helm/papers/calculemus-2003/hbugs-calculemus-2003.tex b/helm/papers/calculemus-2003/hbugs-calculemus-2003.tex index 9ebbc9403..b6425289f 100644 --- a/helm/papers/calculemus-2003/hbugs-calculemus-2003.tex +++ b/helm/papers/calculemus-2003/hbugs-calculemus-2003.tex @@ -430,12 +430,13 @@ the \hbugs{} architecture. pass the control to a second thread, created on the fly, to handle the incoming request following the classical one-thread-per-request approach in web servers design. - If the received request is a Start\_musing one a new thread is spawned to - handle it and the thread in duty to handle the HTTP request returns an HTTP - response containing an identifier of the just started musing. - Otherwise, if the received request is a Stop\_musing one, it should carry a - musing identifier used to identify the thread responsible for a musing. Once - identified that thread gets killed and an HTTP response could be returned. + If the received request is \texttt{Start\_musing}, a new thread is + spawned to handle it and the thread in duty to handle the HTTP request + returns an HTTP response containing an identifier of the just started + musing. Otherwise, if the received request is \texttt{Stop\_musing}, + it carries a \texttt{musing} identifier used to identify the thread + responsible for a \texttt{musing}; that thread gets killed and an HTTP + response is returned. This architecture turns out to be scalable and allows the running threads to share the cache of loaded (and type-checked) theorems. -- 2.39.2