Added limitation on maximum allowable SCOOP processors.

Author:halw
Date:2011-06-21T21:37:36.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@930 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/solutions/concurrent-computing/concurrent-eiffel-scoop/scoop-implementation.wiki

@@ -15,16 +15,24 @@ The differences between the EiffelStudio implementation of SCOOP and current and
 
 =Known limitations=
 
+
 ==Supported concurrency mechanisms==
 
 Although the SCOOP model can support virtually any underlying concurrency mechanism, the initial SCOOP implementation in EiffelStudio version 6.8 supports only one executable, using multiple process threads as SCOOP [[Concurrent Eiffel with SCOOP#Processors|processors]].
 
+
 ==SCOOP processor termination==
 
 In version 6.8, a SCOOP processor, once created does not terminate until the entire SCOOP application that created it terminates. This occurs when all processors in the application become idle, that is, when there are no more calls logged on any processor and no calls are in the process of being applied. 
 
 In a future version, garbage collection will determine when a particular SCOOP processor may terminate.
 
+
+==Maximum number of SCOOP processors==
+
+In the initial release, the allowable maximum number of SCOOP processors per system is 1536.
+
+
 ==Separate anchored types==
 
 Applicable prior to revision number 86657: 
@@ -54,6 +62,7 @@ and the type of <code>my_query</code> is <code>separate</code>, you should make
 
 =Implementation dependent behavior=
 
+
 ==The Wait Rule==
 
 The [[Concurrent Eiffel with SCOOP#Access to shared resources|Wait Rule]] says: ''A routine call with separate arguments will execute when all corresponding processors are available and hold them exclusively for the duration of the routine.''