4 ms·
One small question: if a user has their upload stream redirected to your service, and for some reason this upload is unable to finish, are we now forced to hav
by tstrong 16y ago
One small question: if a user has their upload stream redirected to your service, and for some reason this upload is unable to finish, are we now forced to have the user try the upload again? It seems one advantage of the two step process would be the ability to try the process again on behalf of the user rather than making them wait and that should be weighed into the convenience formula.
I've never used your service so I'm not sure exactly how the upload stream is redirected to your platform, so this concern might not be totally valid if the upload is running through the client platform anyways.
- felixge 16y ago> if a user has their upload stream redirected to your service, and for some reason this upload is unable to finish, are we now forced to have the user try the upload again? If the upload doesn't finish the user needs to redo it. > It seems one advantage of the two step process would be the ability to try the process again You got me confused here. If the upload never finished, there is nothing you can do to fix this. That being said, resumable file uploading is the next thing we'll tackle.
- tstrong 16y ago> It seems one advantage of the two step process would be the ability to try the process again I should have been more specific: consider the special case that the encoder on your side encounters a random error whereas just a "plain" upload to the client platform would have finished, so precluding any network transmission errors. Although, with resumable uploading and a simple go-between service on the client platform between the user and your platform all manner of fanciness could be achieved, I think. Thanks for quick response!
- jemfinch 16y agoYour question is answered in the link itself. Did you read it?