The “missing” piece is that we track which class, logged in user, and some other items in a DB record on the server. We also allow them to upload a text file that is associated with the media (audio/video) and we send out notifications by email, track access when the file is played and some other housekeeping items, so what I am trying to do is retain all that metadata and tracking info for the 1200 classes and 400,000 users we have. ALL of that code is written and tested so I was hoping that when the InputStream arrives at our server from the JS client I could just pass it on to Kaltura, WITHOUT the intermediate stop, basically just passing the stream through while collecting the metadata. The API I looked at needs a path to the file in order to upload it to the server and that is what I have working at the moment. But that means the upload time to our server happens first and then the upload to the Kaltura server is next. Two steps that are unnecessary but that is the API I found.
Using the JS client that you posted might be a way to handle stuff in the future but with so many moving parts in the current application which are needed for our own detailed tracking metrics, I don’t want to have to rewrite too much code.
I get ALL the advantages to having Katura do the heavy lifting on the transcoding and playback piece, wrapping our needs around that is the challenge.