Andrew said:
And in what way do they 'go nuts'?
Or are you suggesting they *silently* deny the install*?
Sure they can - they can then also forget that they
set it that way. There is no accounting for end users.
* In fact, in all cases where something was 'silently'
denied, it turned out the end user had actually done
that (then developed a mental block to the icon on their
browser that *told* them the install was denied).
I fully believe that, but I am discussing your statement,
"peoples' firewalls and anti-viruses will go nuts or even
worse, silently deny the .cab install."
At issue are the terms 'silent' (which they are not unless
specifically told to do so - and even then they usually
have some indication that the user ignores) and 'go nuts'.
Andrew T.
The reason I said that many products will silently 'deny' the execution
of ActiveX scripts is that the user:
1) Might have been infected by spyware (other malware) some time ago.
2) At some point they realize what had happened (could take years).
3) Somebody will suggest they install some a
firewall/anti-virus/spyware blocker
4) They do. The protection software though keeps flashing all these
warnings every time there is an ActiveX trying to execute (or anything
else deemed dangerous)
5) The user gets tired of warnings and just clicks the "Don't show the
warning anymore but keep blocking"
6) They get to the page that tries to automatically install a JDE using
an ActiveX and you (the Java WS application creator) rely on it to
work flawlessly while the user never even sees its prompt for
permission to run.
Anyway, the point was that there will always be some exceptional group
of users that has some strange configuration that will end up having to
do extra work to get an application running via Java WS...