From 17525f1603c0934220a55d068bc540cd10bd6a97 Mon Sep 17 00:00:00 2001 From: Christine Dodrill Date: Sat, 1 Sep 2018 20:45:16 -0700 Subject: [PATCH] blog/olin 1: typo --- blog/olin-1-why-09-1-2018.markdown | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/blog/olin-1-why-09-1-2018.markdown b/blog/olin-1-why-09-1-2018.markdown index adc84fe..0a7db8b 100644 --- a/blog/olin-1-why-09-1-2018.markdown +++ b/blog/olin-1-why-09-1-2018.markdown @@ -30,7 +30,10 @@ When matching data is written to the queue for the event type `example.UserLogin all of the handlers registered to that data type will run with serialized protocol buffer bytes as its standard input. If the handlers return a nonzero exit status, they are retried up to three times, exponentially backing off. -Handlers need to deal with the fact they can be run out of order. +Handlers need to deal with the fact they can be run out of order, and that multiple +instances of them will can be running on physcially different servers in parallel. +If a handler starts doing something and fails, it should back out any previously +changed values using transactions or equivalent. Consider an Olin handler equivalent to a Unix process. @@ -88,7 +91,7 @@ is the kind of API that libc would be implemented on top of. Dagger processes will use [WebAssembly][wasm] as a platform-independent virtual machine format. WebAssembly is used here due to the large number of -implemetnations and compilers targeting it for the use in web programming. We can +implementations and compilers targeting it for the use in web programming. We can also benefit from the amazing work that has gone into the use of WebAssembly in front-end browser programming without having to need a browser!