[mapguide-internals] MapGuide RFC 71 for review
tom.fukushima at autodesk.com
Mon Jul 6 16:21:02 EDT 2009
This will be great!
The concern that I have is that for large selections (thousands of features), this could potentially cause the basic viewer to become substantially slower. Can we add the following requirements:
1) Whatever we do will not increase the time it takes to show the selection in the map? That is, the selection should show on the map first, then the generation of the property panel should be done asynchronously and the user should be able to do other operations while it is being generated.
2) If the properties panel is not visible, there will be no unrequired requests and processing for the properties panel (in client, web tier and server).
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Wednesday, July 01, 2009 9:49 PM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] MapGuide RFC 71 for review
I've posted a new RFC for discussion/review:
View this message in context: http://n2.nabble.com/MapGuide-RFC-71-for-review-tp3193293p3193293.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals