Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>UPDATE: <a href="http://www.idownloadblog.com/2012/06/13/ios-6-safari-media-uploads/" rel="nofollow noreferrer">This article</a> appears to be more relevant.</p> <p>You should chunk the video and hash each chunk using the <a href="http://www.html5rocks.com/en/tutorials/file/dndfiles/" rel="nofollow noreferrer">HTML5 File API</a>. Mobile devices have a lot of errors during transmissions. If a chunk fails, you'll need to request it again. This may not seem like an issue if you're going over SSL or TLS, however, it actually is an issue. The failure rates are really high if you don't chunk the video (because it has to start all over again and the probability of failure during such a large file is quite high).</p> <p>Also, take a peek at <a href="https://www.youtube.com/watch?v=Il4swGfTOSM" rel="nofollow noreferrer">this video</a>. It will further explain some details of transmission patterns of radios in mobile devices. There are further references at the end of the talk for even more details.</p> <p>As for how to bypass the UIWebView behaviour, you may want to try intercepting the HTTP request and writing Objective C code to manage the uploading. See <a href="https://stackoverflow.com/questions/12844598/send-custom-headers-with-uiwebview-loadrequest">this article</a> for implementation details. </p> <p>Lastly, I'm not sure how successful you'll be with a UIWebView only implementation (ie. not writing Objective C). UIWebView seems to be aggressive (and inconsistent) about how much memory it lets you consume before it forcibly closes your web page.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload