Changes between Version 9 and Version 10 of MapGuideRfc110

Timestamp:

04/21/11 23:20:34 (14 years ago)

Author:

liuar

Comment:

--

MapGuideRfc110

@@ -198 +198 @@
 
 Solution 1.
-Copy the implementation of profiling related APIs to !MgServerProfilingService and add profiling code into the copied version, for example, copy the implementation of !RenderMap in !MgServerRenderingService(and all other MG server APIs invoked in !RenderMap) to !MgServerProfilingService. The advantage and disadvantage of this implementation is obvious: less influence on the origial implementation but heavy maintainence to do in the future.
+Copy the implementation of profiling related APIs to !MgServerProfilingService and add profiling code into the copied version, for example, copy the implementation of !RenderMap in !MgServerRenderingService(and all other MG server APIs invoked in !RenderMap) to !MgServerProfilingService. The advantage and disadvantage of this implementation is obvious: less influence on the original implementation but heavy maintenance to do in the future.
 
 Solution 2.
 Inject the profiling code into the functions being profiled, which means !MgServerServices should be extended to accept a !ProfileResult and the implementation of some APIs will updated to support profiling. For example, to support profiling !RenderMap, all the !MgServerServices in the !RenderMap workflow will be affected - !MgServerRenderingService, !MgServerResourceService, !MgServerFeatureService, !MgServerDescribeSchema, !MgServerSelectFeatures, etc.
 
-For both solustions, how many code should be copied or updated will be decided by how detailed information would be gathered.
+For both solutions, how many code should be copied or updated will be decided by how detailed information would be gathered.
 
 == Test Plan ==