[mapguide-internals] Re: The selection of a feature appears to be inefficient

[Jackie Ng]

The underlying problem is that the native selection APIs
(MgFeatureInformation) only returns properties of *one* selected feature,
regardless of how many objects you have selected.

I thought up of a possible solution to your 3rd point, but then once again
realised that MgFeatureInformation lacks the required information (centroid
for zooming to the selected feature). Ugh!

We really need a "one stop shop" for all your feature selection and tooltip
processing needs, unfortunately the native selection APIs is not it and
RFC71 while solving the limitations of MgFeatureInformation, has introduced
some unnecessary server round-trips as you rightly pointed out.

Thoughts?

- Jackie
-- 
View this message in context: http://osgeo-org.1803224.n2.nabble.com/The-selection-of-a-feature-appears-to-be-inefficient-tp5606625p5633158.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.