Modify only the fragment loader

[stiller-leser]

Modify only the fragment loader

[mangui]

Hi @stiller-leser
not clear, it is up to you to only P2P-load fragment and keep using a regular XHR for playlist loading in your custom loader ?

[stiller-leser]

Hey @mangui,

Thanks for the fast reaction. Sorry I'll try to be more specific. Yes it is up to me. I want to download the playlist for one peer (peer1) and have him load the fragments the traditional way and cache them in his SessionStorage? (not sure where yet). Now if another peer (peer2) connects later on, he would download the playlist and ask peer1, if he could download the fragment from him instead of the server - which is why I only would need to modify the fragment loader.

I am in kind of a R&D phase (thinking about different ways to realize such a peer2peer-approach for my bachelor thesis), so it might change. Also I am aware that this would only work effectively if peer2 connects later - after peer1 has downloaded the fragment. A P2P-connection with the server (in my case via webRTC) would be unrealistic with many peers (bandwidth and performance wise).

Thanks for your support!
stiller-leser

[mangui]

yes, this is what I understood, good luck for your project.
you can easily detect URL type (fragment vs playlist) and use utils/xhr-loader for playlist loading, and your own P2P / WebSocket loader for fragment loading.

[stiller-leser]

Hey,
excuse me for reopening the topic. I hope you don't mind.

By now I found out, that if the load function was called from the PlaylistLoader the responseType would be a String with a length of 0. In the case of the FragmentLoader it would be a String with a length of 11 and the content 'arraybuffer'. This of course enables me to use a simple if statement.

However, as I understand, if I pass the loader into the config, it replaces the standard loader for both the PlaylistLoader and the FragmentLoader. My approach would now be, to create a new XhrLoader in the "Playlist" case and call its load function, just passing on the arguments and use my own load function in the "Fragment" case. Did I understand the principle correctly?

What do you think of a refactoring, that would allow targeted replacement of the PlaylistLoader or the FragmentLoader (via two config options)?

Thanks and sorry again for reopening,
stiller-leser