News for hackers. Stuff that matters.
Re:Realtime encoding - over 150x faster by felixge on Monday December 20, 2010 @03:26PM (#2025654)
> 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.

Re:Realtime encoding - over 150x faster by tstrong on Monday December 20, 2010 @03:37PM (#2025682)
> 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!

Re:Realtime encoding - over 150x faster by jemfinch on Tuesday December 21, 2010 @01:28AM (#2027140)
Your question is answered in the link itself. Did you read it?