Last post Jul 22, 2015 11:06 PM by TheNutCracker
Jul 15, 2015 03:18 PM|TheNutCracker|LINK
pretty much instantly, one right after the other. Is this a problem for IIS? Do I need to stagger each XMLHttpRequest by putting time delays between each request? Is IIS purposely dropping some requests because of how fast they are coming in or how close together
they come in? My only theory right now is, its too much too fast.
through a file upload. And no request were lost. All HTTP codes returned were 200 OK.
The XMLHttpRequest goes out with async = true as Chrome forces this setting for performance reasons. But my action method server-side that handles the incoming file chunks isn't using async, Task<T>, or await. Is that what I need to do? It's either that
or stagger my XMLHttpRequest on the client. Anyone, anyone? Buehler, Buehler?
Jul 16, 2015 04:32 AM|PatriceSc|LINK
500 is a server side exception for which you should be able to find more details. Try
http://www.geekswithblogs.net/shaunxu/archive/2013/07/01/upload-file-to-windows-azure-blob-in-chunks-through-asp.net.aspx (Azure but principles should apply as well).
Jul 16, 2015 10:39 AM|TheNutCracker|LINK
I've discovered that this may be an issue with trying to write multiple chunks to the same file virtually simultaneously. I've opened the file using the System.IO.FileShare.Write option. I am not sure if the issue is fully resolved yet. Still working on
Jul 16, 2015 10:08 PM|Krunal Parekh|LINK
Try using https://blueimp.github.io/jQuery-File-Upload/ jQuery file upload. It will handle the XMLHttpRequest by it self on the sever side you just need to get the Request.Files Directly.
Hope this helps. You could also try to upload using directly jquery ajax. Please see:http://abandon.ie/notebook/simple-file-uploads-using-jquery-ajax
in the ajax call set async to true to make upload async.
Jul 18, 2015 09:05 PM|bruce (sqlwork.com)|LINK
Jul 18, 2015 10:51 PM|TheNutCracker|LINK
Why separate requests? Because IIS Server has a 30MB maximum request length limit. ASP.Net has a 4MB request length limit. Which is even more restrictive. Uploading files in chunks gets around these limitations. There is overhead in anything that requires
error checking. Are you sure you are scolding me properly? :)
I've found that the .NET framework API will allocate chunks as needed.
Not sure what to make of your post. It seems to be saying a lot of contradictory things all at once.
How would I send all chunks over a single request? I am very interested in learning that trick. Surely, the devil is in the details and not your words. By the very nature of uploading a file in chunks, I would think there is a lot of chatter between the
client and the server.
Jul 22, 2015 09:46 PM|Krunal Parekh|LINK
Try using Jquery's Chunkfileupload size that way you can send large amount of data from client side.
maxChunkSize: 10000000 // 10 MB
Hope this helps.
Jul 22, 2015 11:06 PM|TheNutCracker|LINK
Well, yes, I will go out on a limb here and say that this accomplishes what I am trying to accomplish. But it looks like it's jQuery doing it and not me. :)
I was trying to learn how to fish. Not looking for a free fish.
On second thought, since jQuery is open-source....I can go study the source code and then practice molding it into my own special shape. So, this will be very helpful to me.
Thank You for your post!