3 ms·

> Hang on - you said "from local storage". The video is played from server-side storage. If it was on local storage on the client, you could only play it on tha

> Hang on - you said "from local storage". The video is played from server-side storage. If it was on local storage on the client, you could only play it on that client. So I take it you meant "local to the server", in contrast to online video resources. Bingo. In switching over to pet project thought mode I started thinking "local to myself" rather than the usual client-server wording. Thanks for the advice! That sounds genius. I can much more easily imagine implementing this with my existing skills compared to figuring out how to script VLC or some other media player. Now I'm guessing this approach serves the server media file to the client browser, and the client browser then plays it locally. Would it be possible to create a kind of TV-channel/radio-station type of approach where the server is constantly playing a video, and any client on the network can hop onto the stream like a TV channel?

denton-scratch 5y ago
The <video> tag also has a javascript model you have to learn, like with VLC. It gets video in junks, on request from the browser; if nobody's requesting chunks, no chunks will be played. You can't play if there's nobody listening. It doesn't serve files. If you start a new item, it begins to play immediately - it doesn't seem to need to buffer. I imagine your media channel thing can be done, but I haven't tried it or thought about it. Not my use-case! It's not "genius", BTW - I'm no media expert, not even a very good programmer. I'm just a tinkerer with an itch to scratch. And there's no way I'm sharing my code - it's a pile of crap, permanent work-in-progress. I like the <video> tag very much, because it's cross-browser, and (IMO) is easier to script than previous players.