picocandy / rubytus Goto Github PK

tus 1.0 is just around the corner. I would be pleased to see this implementation being updated to support the next version. Most updates are outside the core so only minimal changes are required to maintain comparability. You can find detailed information or get feedback at the according issue tus/tus-resumable-upload-protocol#57.

Are there any examples or documentation on how this would integrate with a rails application?

First of all, thank you for sharing this with the world, it was very inspirational to dive into the source code.

But I'm curious, why does Rubytus use Goliath instead of a regular synchronous framework? I feel like using EventMachine is awesome when you're doing a lot of IO (e.g. HTTP requests), because then everything is asynchronous. But Rubytus only writes to filesystem, which is very fast. And even if it's not, it's currently still synchronous.

So just out of curiosity I wanted to know why did you decide to use Goliath? Is it because of its ability to terminate the request before the request body is received?

We were trying to run tus-ruby-server behind a reverse proxy via SSL and noticed that rubytus doesn’t have the “behind proxy” feature yet. Would you be able to add this feature considering the importance of SSL?