Hi @phelgren,
In regards to the Java code you’ve been looking at, this repo is better:
because it supports uploading several chunks in parallel.
What I don’t understand though, is why you need to upload the file from the client to an intermediate server to begin with? Since Kaltura’s ingestion flow also includes transcoding [using FFmpeg] to multiple, customisable flavours, you can skip what you currently do with Java and upload the user’s source file [as received from the JS client code] directly to Kaltura and the transcoding will then take place, on Kaltura’s servers.
However, if the file is already on that intermediate server, then why can’t you use https://github.com/kaltura/kaltura-chunked-upload-test as is? It already accepts a path to the file and you have that path on the server’s local FS… what am I missing?