Java Applet Versioning Issues: Need adivce on consolidating an Applet

My company uses an applet that resizes images on the user's computer and then uploads them in a zip file to our company抯 servers. We would like to support all versions of Mac Os X; however, since only tiger and leopard support Java 1.5, and our resizing code does not run well in any other runtime (due to out of memory errors and really poor performance), we are requesting users of earlier Java runtimes to resize their images before uploading.

This has forced us to have two versions of the applet a 1.3 version and 1.5 version. For PC users, we use an Active X control to resize images; this is very fast, and we cannot beat the speed even with the 1.5 version on PC. However, we are currently using the Java 1.3 code tree for PC users. My questions are

1) Can we consolidate both code trees without doubling the size of the jar file?

2) Will upgrading the PC version, which does most of its work in the Active X control, gain anything noticeable by being upgraded to 1.5?

[1003 byte] By [PacifistKa] at [2007-11-26 15:58:35]
# 1

> My company uses an applet that resizes images on the

> user's computer and then uploads them in a zip file

> to our company抯 servers. We would like to support

> all versions of Mac Os X; however, since only tiger

> and leopard support Java 1.5, and our resizing code

> does not run well in any other runtime (due to out of

> memory errors and really poor performance), we are

> requesting users of earlier Java runtimes to resize

> their images before uploading.

I have to ask, why (and how) would you possibly resize the image on the client machine?!

> This has forced us to have two versions of the

> applet a 1.3 version and 1.5 version. For PC users,

> we use an Active X control to resize images; this is

> very fast, and we cannot beat the speed even with

> the 1.5 version on PC. However, we are currently

> using the Java 1.3 code tree for PC users. My

> questions are

>

>

>

> 1) Can we consolidate both code trees without

> doubling the size of the jar file?

I think you're going in the wrong direction. Pick a version and stick with it. Don't support 2 versions unless you absolutely have to.

> 2) Will upgrading the PC version, which does most of

> its work in the Active X control, gain anything

> noticeable by being upgraded to 1.5?

What do you mean by upgrading the PC version? I seriously doubt this will have much impact, assuming you're at least using Win2000 or later. And what are you doing with ActiveX? ActiveX and Java don't (ideally) have anything to do with each other.

CarrieHunta at 2007-7-8 22:19:42 > top of Java-index,Desktop,Core GUI APIs...