Corysia,
We're all familiar with the auto_install information.
You're missing the whole point. You are pointing to a a piece-meal
strategy. What we are saying is that Sun should look at deployment for the
overall Java strategy and only install those components which are needed,
when they are needed. They should auto-update as well.
Are we the only ones that feel this pain? I don't believe so from the
volume on the list of related items. So far Sun has been unwilling to
subset Java and because of this the initial Java download is rather
large. Then add to that J3D, then your application code, then your
content... It gets a bit out of control. As far as code and content, we
are already working on streaming it. It's what comes before our code that
is the brunt of the issue.
--Mark
At 11:27 AM 5/11/2001 -0600, Corysia Taware wrote:
>Keep in mind that in the very near future, you'll be able to auto-install
>Java3D directly over the net.
>
>Remember this article?
>http://www.j3d.org/tutorials/quick_fix/auto_install.html
>
>And here's the response when I asked when the Java3D 1.2.1 signed jars would
>be available. When this is live, installation should be a breeze.
Mark Ferneau 240-462-6262 (cell)
Director of Adv. Technology 801-437-4608 (efax)
Xtivia Technologies, Inc. 732-248-9399 x629 (NJ office)
[EMAIL PROTECTED] 301-279-5703 (home office)
http://www.xtivia.com/ [EMAIL PROTECTED] (wireless email)
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".