| 97 | | The quantization algorithm uses lots of resources. 3 different memory allocation schemes have been provided. Selecting those is supposedly too specific to warrant a server option entry. However, the correct approach needs to be decided by a system architect with deeper insight into the MapGuide architecture. |
| | 97 | 1. The quantization algorithm uses quite some memory. 3 different memory allocation schemes have been provided. Selecting those is supposedly too specific to warrant a server option entry. |
| | 98 | However, the correct approach needs to be decided by a system architect with deeper insight into the MapGuide server architecture. |
| | 99 | 2. Is it sufficient to scan the colors from only the VectorLayerDefinitions and in there the Area, Line, and Point Symbolizations ? |
| | 100 | 3. How do we deal with color expressions? Are there some specs for this? |
| | 101 | The current code is based on the existing XML schemas only (and the color definitions I could find in them) |
| | 102 | 4. Following ResourceId references is also not implemented. Is this crucial? |
| | 103 | 5. Memory issues: I think the current approach follows an easy producer consumer style regarding the color tables. |
| | 104 | Again, my insight into the server architecture is limited and I am not 100% sure if all possible memory leaks have been avoided. |
