Welcome to the new Uploadify Community Forums. We've made the switch from PHPBB to Vanilla Forums in hopes of controlling the SPAM more efficiently. We hope this change doesn't suck so much. Also, don't forget to wrap your code in tags. You can quickly insert code using ctrl + f.
I lost some messages that were posted on February 4th. If you posted a message or reply on February 4th, please do so again. Sorry about the inconvenience.
File API alternate use
  • Hi

    Would it be possible to modify Uploadify to use the File API when available (Firefox 3.6) ?

    I think using the API could be done without changing the UI at all, and would provide a Flash-alternate solution for Firefox 3.6 users (and others later on? -- with newer browsers).

    I know that Flash is the backbone of Uploadify, so this suggestion might not be accepted just because of this. What I want is the honest answer from you guys, about the possibility of such an implementation. Whether to actually implement it or not would be another story, and I'm quite prepared to do that myself anyway (as a new plugin).

    Thanks,

    passcod
  • the File API is certainly a possibility and should resolve a lot of issues flash causes, however it needs to be supported by a majority of browsers. I feel swapping uploadify over to the File API will restrict users to using the latest versions of browsers. As many people are still haven't upgraded their version of IE it can count out a lot of users. And on that who knows when IE will even write the new standard into their browser? I believe fairly certain that safari, chrome and opera will adopt the standard, but again the question is when? Remember the File API only entered into official draft in November 2009.

    There is a way to do it and that is to test the version of browser being used and then use one version built with flash or if a valid version, use the File API. This adds alot of overhead to the plugin and Ronnie may feel it goes against the foundations of uploadify.

    We'll just have to wait and see
  • BufferedReader is one of the two best API to use for this.If you really had trouble with file reading, an alternative might be to use the stuff in NIO to memory-map your files and then read the contents directly out of memory.But your problem is not with the reader. Your problem is that every read operation creates a bunch of new objects, most likely in the stuff you do just after reading.You should consider cleaning up your input processing with an eye on reducing the number and/or size of objects you create, or simply getting rid of objects more quickly once no longer needed.
  • There's a much simpler way to test for this. No point in checking browser versions. Available when FileReader != undefined.

    And yes, I would also be really glad to see support for File API built into uploadify.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!