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

[Zac Spitzer]

Hi Gabriele,

I share your concerns about how selection currently works, changing
this would require an RFC. mulitple round trips with network latency really
affects the user (and developer) experience

z



On Thu, Oct 14, 2010 at 10:40 AM, Jackie Ng <jumpinjackie at gmail.com> wrote:
>
> 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.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168