Which is better when it comes to File Uploads? I don't mean wimpy 50MB or 100MB uploads, I'm talking about something like 500GB to 2GB of uploading maybe more. (not past 5GB)

I have found that;

1. Standard HTML upload = sucks
2. Ajax upload, the same but = sucks
3. Flash to be = dependable at times
4. Java somewhat = feature-ful

So what is the same? I don't know how to make java applets or flash upload systems but i can learn, i just need to be pointed in a direction...

It just depends.

Flash is can be useful because it's ubiquitous. However, Java come with much more power. You could use it to segment files to ensure much greater reliability with a large upload especially on flaky connections.

Your main issue with using a Java applet is, in order to reference a local file (to upload), the applet will need to be signed and the user will need to grant the applet permission to read local files.

So in other words, you are saying that Flash is quicker and a little more user friendly, correct?

I am a developer and have developed several websites. I have not faced any problem with standard http uploads. However, this is limited for small files. If the file to be uploaded is of 1 GB or so, it is always recommended to use the java applet to upload it.

Originally Posted by microcolt

So in other words, you are saying that Flash is quicker and a little more user friendly, correct?

I doubt flash would be any faster. Your bottleneck will be the network, regardless of how you do it.

The user-friendliness is up to you, not the language or runtime

Though, by being able to partition files in Java, I could potentially be more user-friendly on flaky connections.

Originally Posted by willcode4beer

I doubt flash would be any faster. Your bottle neck will be the network, regardless of how you do it.

The user-friendliness is up to you, not the language or runtime

Though, by being able to partition files in Java, I could potentially be more user-friendly on flaky connections.

When you say "network" are you talking about speed or in how i present the system its self?

Originally Posted by microcolt

When you say "network" are you talking about speed or in how i present the system its self?

When I say "network" I mean that thing with the wires you use to transmit data

By bottleneck, I mean, the limiting factor regarding speed

Checkout SWFUpload, that is a great open source flash uploader. I have used it many times and love it.

Thanks but i need a HTTP uploader.

Which is better when it comes to File Uploads? I don't mean wimpy 50MB or 100MB uploads, I'm talking about something like 500GB to 2GB of uploading maybe more. (not past 5GB)

I have found that;

1. Standard HTML upload = sucks

I think that what you call "html standard" is just php - after all, you show no indication of knowing how to handle it in perl

I have observed that aspx uploading is a hell of a lot slower than perl, but I've never tested php - although php is obviously worse, as a language, than both aspx and perl.

I think you just need to try doing it with perl. Perl uploading is no doubt faster than php - maybe then you won't need to use inappropriate platforms like flash or java (the latter will be denied permission too much and the former is for making animated graphical objects, not file system commands!)