Changes between Version 11 and Version 12 of MapGuideRfc60

Timestamp:

May 10, 2009, 5:03:24 AM (15 years ago)

Author:

uvlite

Comment:

--

MapGuideRfc60

@@ -62 +62 @@
 The base colors of a map can be extracted most efficiently during map generation in MapingUtil::StylizeLayers().
 To do this the VectorScaleRange gets an additional method called VectorScaleRange::GetUsedColorList().
-This is a computed property implemented as a singleton which creates the list upon access. Subsequent requests from other threads read the same list. The singleton is not protected with a mutex as a second thread would recreated the same datastructure....in the worst case I can imagine a few kBytes of memory leak with a very low probability.... more costly than the mutex I suppose. 
+This is a computed property implemented as a singleton which creates the list upon access. Subsequent requests from other threads read the same list. The singleton is not protected with a mutex as a second thread would recreate the same datastructure....in the worst case I can imagine a few kBytes of memory leak with a very low probability.... less costly than a mutex I suppose. 
 
 At the end of the stylization GetUsedColorList is called and the resulting color list is stored in the runtime map object MgMap.
@@ -99 +99 @@
 
 2. The quantization algorithm can use quite some memory. 3 different memory allocation schemes have been provided. [[BR]]
-Due to recent problems in low memory situations a choice has been made to use the most conservative stack based allocation scheme.
+Due to recent problems in low memory situations a choice has been made to use the most memory conservative stack based allocation scheme.
 
 3. In this phase only the colors from the VectorLayerDefinitions and in there the Area, Line, and Point Symbolizations are parsed