MWABP 20091704: comments (correction)

A correction to my previous comments:

"Scripting enabled" actually corresponds to a property to be communicated to
the server. Obviously, it is somewhat tricky to detect the status of this
attribute from a local script if scripting is disabled. In any case, letting the
server know whether scripting is enabled or not allows it to generate pages 
relying upon scripts or not. The property must also be set for the entire 
duration of at least the HTTP transaction (otherwise scripts will not be 
downloaded or executed) -- and it is dubious whether one is fast enough to 
toggle the property before the browser has had a chance to take some decisions
upon the previous state (i.e. downloading or not scripts, launching or not the
scripting run-time engine). There are MIME types corresponding to scripting 
languages, which are presented in the usual HTTP header fields -- and I believe 
some browsers, such as the Blackberry one, include or not MIME types in their
HTTP requests depending on whether the corresponding facility is activated.

Conclusion: Whether the execution of applications is driven by properties to be
dealt with on the terminal or on the server requires a careful analysis according
to the four elements I mentioned in my previous mail.



Received on Wednesday, 29 April 2009 13:36:43 UTC