>Javier Borrajo wrote:
>> But since you raise the fat client issue, Win2000 has a revamped
>> Installer that makes automatic network installation, repair and
>> upgrade of client apps so easy and versatile it takes away a lot of
>> the reasons to develop so called Java thin-clients -- a Java applet
>> may be one of the fattest clients you can find, with above 20 MB RAM
>> usage including the browser, and well above of 1 MB of
>> downloadable code each time the client starts.
>
>That is only partially correct. The current Java2 environment requires
>this, but the next (JDK1.3) provides client caching mechanisms for
>applets, so that the code is only downloaded once. I.e., the way the W2K
>installer works, only it works on all platforms and not only with W2K
>clients. While it may be feasible for a company to update all of its
>servers to W2K, I think there is much more resistance to update all
>clients as well considering the cost.
We may see companies never moving from Windows 3.1/NT 3.51, while
others migrate massively into W2K. IBM anounced recently it has plans
to buy 300.000 W2K licenses. It depends what you find in the field,
and it's good to know you have options to choose from.
>> Anybody who deploys Java applets must be considering several schemes
>> to install part of the client in the user's workstation, be it CAB files,
>> PVCj or Marimba/Castanet. Windows 2000 Installer is just that.
>
>Again, with the introduction of JDK1.3 this is a non-issue. It's
>built-in now.
It's nice to know the future is so full of promise! ;-)
Best regards
Javier
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
