I'm not sure of the performance differences between between WMS and the MapGuide layer, but there is a patch available for the OL MapGuide layer that removes the asynchronous behaviour in the MapGuide Layer. See: http://trac.openlayers.org/ticket/1756. This is currently marked for review in the OL Trac system. I'm not positive about the MGOS version numbers but I believe this works with MGOS2.0.2?
Mike gingerbbm wrote: > Brilliant. Thanks chaps :) > > The question now becomes: is there any preference between using > OpenLayers.Layer.MapGuide and OpenLayers.Layer.WMS (which I've been using up > until now)? The WMS is simpler to implement (no session ID required). > Furthermore there's this warning from the MapGuide class's API > documentation: > > "NOTE: untiled overlay layers issues a synchronous AJAX request before the > image request can be issued so the users browser may lock up if the MG Web > tier does not respond in a timely fashion." > > If the WMS call isn't synchronous (is it?), then there appears to be two > good reasons to use it instead of the MapGuide class. > > Thoughts? > -- Michael Adair Senior Software Architect DM Solutions Group Inc. Office: (613) 565-5056 x26 mad...@dmsolutions.ca http://www.dmsolutions.ca http://research.dmsolutions.ca _______________________________________________ Users mailing list Users@openlayers.org http://openlayers.org/mailman/listinfo/users