depending on what your doing! wms ain't cached by mapguide whch s fine if your doing dynamic maps, but if you need to serve more than a few users, your gonna hit performance issues....
I remember that Mr adair has patches in place for addressing some of that, have a look at the OL trac the session id stuff is only required for dynamic maps... which is useful when your doing funky stuff with the map, of course when your not, it's a big old pain in the butt, catch-22 yosarian.... there's quite a case for a review of mapguide to make it more openlayers friendly, z On Sat, Jan 17, 2009 at 1:21 PM, gingerbbm <stuart.jo...@jacobs.com> 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? > -- > View this message in context: > http://n2.nabble.com/MapGuide-overlay-session-ID-requirements-tp2169448p2171721.html > Sent from the OpenLayers Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users@openlayers.org > http://openlayers.org/mailman/listinfo/users > -- Zac Spitzer - http://zacster.blogspot.com +61 405 847 168 _______________________________________________ Users mailing list Users@openlayers.org http://openlayers.org/mailman/listinfo/users