Unlike the AJAX viewer, the development platform in Fusion is not PHP/.net/Java. It is javascript.
The only time PHP/.net/Java is involved is when you need to cover functionality that is not exposed by the HTTP mapagent or you have a need to integrate with 3rd party web applications/services. And in this respect PHP was chosen for the Fusion backend because: 1. It works on both Windows and Linux 2. No JRE or netfx redistributable requirement. 3. Zero-configuration. No need to setup/configure virtual directories and/or servlet containers. 4. Regardless of your installation options, PHP is always installed (as it is required by the Site Administrator) Yes we could have a .net or java Fusion backend, but that is a clear violation of DRY and is pretty pointless for a *client-side* framework like Fusion. The AJAX viewer *had* to exist in 3 different languages due to its pre-web2.0, frame-based, server-centric design. Fusion does not, but that doesn't mean your server development platform is restricted to PHP. There is nothing stopping you from having .net/java Invoke URL commands in Fusion, and there's nothing stopping you from creating new widgets with .net/java backends. It's just that the server-side infrastructure in Fusion is done in PHP, I presume, is because it is the language with the broadest platform reach for the reasons already stated above. - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Use-tile-cache-in-different-maps-tp7054653p7061509.html 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
