My experience with uploading is that you have to code it for failures. If
you could test the quality, it might be unacceptable for your purposes,
but then a second later it could be great and the user would miss the
opportunity or window you were shooting for.

I think it is best to begin optimistically and throttle back as you
receive feedback from your server. IMO, your server code should be written
to accept your uploads in chunks. You can tell on the mobile side the
round-trip time as each chunk goes up. Perhaps your server can tell you
the last good data chunk it got in case you need to restart. That way you
don't have to re-send.


Peter Ent
Adobe Systems

On 7/11/14 5:52 AM, "Tom Chiverton" <[email protected]> wrote:

>Yeah - they could have a great connection, but then the train goes into
>a tunnel...
>
>Tom
>
>On 11/07/14 10:40, Frank Dahmen wrote:
>> thanks,
>> main reason was maybe not to have to worry about canceled/broken
>> uploads (cache the data)
>> but i think i have to anyway
>>
>>
>> Am 11.07.2014 11:24, schrieb Tom Chiverton:
>>> You could optimisticly try the upload, and use the progress events to
>>> gauge the speed.
>>>
>>> Tom
>>>
>>> On 11/07/14 10:19, Frank Dahmen wrote:
>>>> Hi,
>>>>
>>>> is there a way to get the mobile network quality in air mobile like
>>>> edge, 3G etc.?
>>>> I would like to advise the user to start an upload later if network
>>>> quality is bad (or even disable the upload).
>>>>
>>>> Thanks
>>>>
>>>>
>>>> ______________________________________________________________________
>>>> This email has been scanned by the Symantec Email Security.cloud
>>>> service.
>>>> For more information please visit http://www.symanteccloud.com
>>>> ______________________________________________________________________
>>>>
>>>
>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud
>>service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>>
>

Reply via email to