Although this
configuration could be automated to a certain degree, it resulted in two show-stopping
points for many.
Figure 1-2. Sophisticated browser architecture
CHAPTER 1 ?– INTRODUCING AJAX 4
First, it didn??™t always work, as the nature of the configuration, changing the Windows
registry, often failed??”or worse, broke other applications. ActiveX controls were rarely
self-contained and usually installed runtime support files. Different versions of these
support files could easily be installed on top of each other??”a common occurrence
leading to broken applications (called DLL Hell).
The second problem was security. A user??™s computer, when connected to the Internet,
could effectively allow code, written by anybody, to run. The ActiveX technology was
fully native, not restricted by the Java or HTML sandboxes (more about these in a
moment); therefore, users could innocently go to a web page that downloaded an ActiveX
control and wrought havoc or stole vital information from their systems. As such, many
users refused to use them, and many corporate administrators even disallowed them
from use within the enterprise.
Pages:
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42