Skip to main content

iOS app: Uploading multiple files in the background



For iOS, I am aware that apps can upload in the background, as according to this thread: Uploading in background thread in iOS





When I refer to "background", I mean the user has clicked the home button, using another app, or the phone's screen is off.





Follow-up Questions:





1. Is there a timeout limit to the background uploading? This may be an issue if the file being uploaded is huge.





2. Is it possible to upload a list of files in the background, or does it only support the finishing of one upload that was in progress before the user switched to another app?





3. I suppose if the user quits the app completely, the upload will be stopped? Quitting completely as in, user double clicks home button, touches and holds down on the app until it starts shaking, then clicks the "X" to shut it down.


Comments

  1. Answers:

    1) The timeout limit is probably server - imposed, but you can certainly add some timeout detection code on the client (iOS) side.

    2) Uploading a "list of files" is effectively the same as uploading a file. A list of files is just another file, effectively.

    3) If the app is killed, yes, everything (and all the background threads) get killed along with it.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex