1

(0 replies, posted in Core API)

Hello,
I am using the BeforeUpload event to change the chunk_size setting on the uploader, but it is creating a strange error. For some reason, the upload gets submitted twice. I have no idea why.

Is it possible to change chunk_size in the BeforeUpload event?

2

(3 replies, posted in General discussion)

I figured out what I was missing: a way to handle CORS preflight requests on my node server.

Here is what I have now:

app.all('/', function(req, res, next) {
      res.header("Access-Control-Allow-Origin", "https://domain.com");
    res.header("Access-Control-Allow-Headers", "X-Requested-With");
     
    if (req.method.toUpperCase() === "OPTIONS"){
        res.header("Access-Control-Allow-Methods", "GET, POST, OPTIONS");
        res.header("Access-Control-Max-Age", 3600); // Seconds.
        res.writeHead(200, { 'content-type' : 'text/plain' } ); //Send success code                   
        res.end();
    } else {
        next();
    }
   
});

3

(3 replies, posted in General discussion)

Flash is working fine.  This is now just an HTML5 problem.

4

(3 replies, posted in General discussion)

I have confirmed that the problem is not ssl, or the absolute url.  It definitely has to do with the fact that it is cross-domain.  On my node.js server, I respond with the headers:

res.header("Access-Control-Allow-Origin", "https://formhost.com");
res.header("Access-Control-Allow-Headers", "X-Requested-With");

As I said above, this configuration works fine with a jquery ajax request, but not with plupload, what is the difference?


I'd really appreciate some help on this.  Thanks.

5

(3 replies, posted in General discussion)

I can't seem to get plupload to accept a destination url pointing to a different domain.

For the sake of example:
The plupload files, and my html form are hosted at 'https://formhost.com'

The parsing app is hosted on a node.js server at 'https://uploadparser.com'

My app at uploadparser.com is configured to send a response allowing for the request host 'https://formhost.com'.  Everything works fine if I just send a jquery.post request, so I know that I am not in violation of the same origin policy.

It appears that plupload is just skipping over each file that has a destination url it doesn't like.  I'm not seeing any ajax attempts, but my binded listeners function as expected.  For example, if I try to send three files, the BeforeUpload fires three times, UploadComplete once, and there are no errors reported.

Could the issue be https? The absolute url? Cross domain safeguards built into plupload? When I switch the url back to a local, relative path, it works again.

I am working with HTML5. Also, I have 'urlstream_upload : true' (for if/when flash is used).

Thanks!
Joe

Oh, woops, I didn't realize there was a third incoming variable for the FileUploaded listener.  Thanks!

My server side script sends a response to the post request sent by plupload.  How might I receive this data?  It would be awesome if the 'FileUploaded' listener included that data.  Maybe it could be added to the uploader object?

Any ideas?

Hey, quick question... I simply added uploader.start(); to the 'FilesAdded' listener so that users don't need to click 'Begin upload' but it doesn't seem to be working.

Am I missing something?

Thanks,
Joe

9

(16 replies, posted in News)

agentOOjoe wrote:

Unfortunately, the file still gets stored in ram memory in firefox 7 (windows).  Files over 1.5gb are failing because I (the uploader) run out of ram.

So, here is my understanding... the new html5 uploader doesn't work properly in Firefox, or in Safari (windows), or in IE.  Is that correct?

In chrome, it works beautifully.  I just finished a 5.6gb file upload.

Could one of the administrators possibly outline when the new html5 uploader will work properly, and in which browsers?

Thanks


An update: I am stupid!
Months later, I find that the reason firefox was using so much memory is because I had firebug running.  Just wanted to correct myself and say that everything works great in Firefox 7 (under normal conditions).

10

(16 replies, posted in News)

Ok, thanks Davit.  Another issue now... I thought I would give silverlight a try, as a backup to HTML5 still allowing large file uploads.  Unfortunately, this appears to be filling ram memory even faster than html5.  I don't get it.  I thought that using silverlight, or any of the 3rd party uploaders, would eliminate the need to store the file in memory.

This update is proving to be quite bumpy for someone who needs 3gb+ file uploads.  Should I continue to depend on JakobAdams java runtime plugin?

11

(16 replies, posted in News)

Unfortunately, the file still gets stored in ram memory in firefox 7 (windows).  Files over 1.5gb are failing because I (the uploader) run out of ram.

So, here is my understanding... the new html5 uploader doesn't work properly in Firefox, or in Safari (windows), or in IE.  Is that correct?

In chrome, it works beautifully.  I just finished a 5.6gb file upload.

Could one of the administrators possibly outline when the new html5 uploader will work properly, and in which browsers?

Thanks

12

(22 replies, posted in News)

Oh, nevermind. I see that it is.  Bummer

13

(22 replies, posted in News)

Hey Davit,
I'm pumped to hear about large file uploads in HTML5.  I'm going to update my site soon. Is multiple file selection still broken in Safari?

Thanks,
Joe

14

(2 replies, posted in General discussion)

Hey Mace,
The Java runtime is very awesome, but I will say it took me a while to figure out.  It was definitely a challenge for a novice like me. I was in contact with the author and commented about my progress on his website:

http://www.jdams.org/plupload

Good luck!

Thanks for the reply Davit.

I look forward to seeing what you guys come up with!

UPDATE:

I finally got Java to work after Jakob (the java runtime author) graciously provided me with some guidance.  It already appears to be far more reliable, and also considerably faster than using Silverlight.

For those who are interested:
http://www.jdams.org/plupload


Would still love to see Java support included with Plupload!

Hello,
I am working on a project to allow for up to 5gb uploads.  From research I have found that the two best options at this time are Java, or Silverlight.  I tried to implement the Java runtime by JakobAdam but was unable to get it working correctly.  I would LOVE it if plupload would come standard with a Java option.  I read in these forums that you guys have been thinking about it for over a year now.  Any news?

Anyway, I am now working with my second choice: silverlight.  I found that I was unable to upload anything past about 2gb unless I used chunking.  Does this make sense from a plupload developers perspective? I read that it is supposed to make all the difference when using flash, but should this also apply to Silverlight? I would prefer to not use chunking if possible.  It makes the process just one step more complicated, and appears to be slowing uploads.  The upload speed sort-of comes and goes in consistent bursts.  I assume that is because of the additional tasks it performs between each chunk.

So my questions are:
1. Should silverlight require chunking for large files (2gb+)?
2. When will we see Java in plupload!?

Thanks for your wonderful work,
Joe