Re: ActiveX versus Client Installer
From: Malke (noreply_at_invalid.com)
Date: 03/30/05
- Next message: Monk: "Re: Want Friendly Logon Screen after auto logoff"
- Previous message: Alan Wilcox: "Re: Roaming Profile won't connect"
- In reply to: Ben: "ActiveX versus Client Installer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 30 Mar 2005 05:55:19 -0800
Ben wrote:
> Hi all,
>
> The company I work for has build a completely browser based
> application. As a sales argument we say that you don't need to install
> a (fat) client on your user machines. However, our application only
> runs in the browser if you allow a browser plug-in (ActiveX) component
> to be installed. Some people say that allowing an ActiveX component is
> in principal the same as providing a client installer.
>
> The following questions:
> 1) Do companies differentiate between client installers and allowing
> ActiveX components, or are the two the same to them?
> 2) Does a Browser plug-in require more setup (deployment) and
> maintenance cost than a client installer?
> 3) Is it possible (from a client viewpoint) to limit the ActiveX
> component (f.e. allow everything, except file-system access)
>
Please see the detailed and useful answer you got in the other
newsgroup. Please do not multipost. Crosspost if you must, judiciously.
Here is a link explaining about multi- and crossposting.
http://www.blakjak.demon.co.uk/mul_crss.htm
Malke
-- MS MVP - Windows Shell/User www.elephantboycomputers.com In Memoriam - MVP Alex Nichol The world is diminished without him.
- Next message: Monk: "Re: Want Friendly Logon Screen after auto logoff"
- Previous message: Alan Wilcox: "Re: Roaming Profile won't connect"
- In reply to: Ben: "ActiveX versus Client Installer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|