From 513382f33bb2037ec3f71426b184390b46181f39 Mon Sep 17 00:00:00 2001 From: halw Date: Sun, 4 Sep 2011 18:04:13 +0000 Subject: [PATCH] m Author:halw Date:2011-09-04T18:04:13.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@968 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../concurrent-computing/concurrent-eiffel-scoop/index.wiki | 1 + 1 file changed, 1 insertion(+) diff --git a/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki b/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki index a9d99e3e..59cae5c2 100644 --- a/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki +++ b/documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/index.wiki @@ -187,6 +187,7 @@ In concurrent Eiffel with SCOOP things are different. This is because a particul {{definition|Asynchronous feature call|A feature call which causes the “logging” of a request by a client for the associated feature application to be executed by the supplier’s processor. }} + After an asynchronous feature call, the execution of the client proceeds immediately, possibly in parallel with the application of the feature on some other processor. We'll revisit this point after a look at what it takes for a call to be synchronous or asynchronous.