Seems that turning to JavaScript is unavoidable at the moment :-) But it would be nice to have this possibility of map/layer refreshing from the server side, too. Here's why...
I created couple of web services (currently on SOAP) talking through my dll on server side with MG libraries. Depending on complexity, certain calls may take some time to perform. JavaScript executes on client, so it's out of synch with server-side execution. Signalling between client and server is sometimes hard to maintain, plus it involves extra HTML elements for handling data between ASP.NET and JavaScript. And it doesn't save any calls. Say, a developer utilizing my server-side library and ASP.NET templates has a button that runs some time-consuming server-side operation. Operation finishes and stores the result (e.g. SelectionXML) in a hidden element that gets read by JavaScript after the page has been posted. Since postback calls get trapped by Ajax.NET, there's a fat chance that my JavaScript will not execute as planned. Etc. Regards, Maksim Sestic Kenneth, GEOGRAF A/S wrote: > > It sounds as if you want to do a "server push" rather than the more > common "client pull". > I'm not sure that it is easily accomplished, but since the AJAX viewer > contains a lot of JS code, I don't see any problems in an extra refresh > call. > -- View this message in context: http://www.nabble.com/Refreshing-a-map-layer...-from-server-side%2C-avoiding-JavaScript-tf4782233s16610.html#a13722292 Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
