Cart
[Home] [By Thread] [By Date] [Recent Entries]
Hello Jeff, Jeff said: I visited the Google Maps people here in Sydney a few months ago. They told me they browser sniffed, and used VML client-side if IE was being used and rendered to JPEG server-side otherwise. (Something like that.) The ability/decision to optimise delivery based on the capabilities is very pragmatic. Didier replies: Good point. Several AJAX development team take the approach of interpretation platforms. Mozilla is a particular run-time, IE is another, Opera another, etc... Idem in the Java world where the IBM platform is different form the Sun platform. This could be at the JDK level or at the virtual machine level. Here is a general engine operation sequence for an AJAX engine a) Recognizing the platform (this can be done at the client or the server level) b) select and load the appropriate software elements c) interpret both the declarative code (i.e. HTML) and the imperative code (ECMAScript/javascript) At the recognition level, if we do not have the required capacities we simply tell the user and possibly provide links for them to download what is required. Idem in the Java world when you need a certain run-time VM. Cheers Didier PH Martin
|
