I have an api such as:
[GET] API/video? ID = {} VIDEOID
Which clients will pass their authorization token in the header to receive video streams from the service (I don’t want people without permission to access protected videos on the service – just Like a private video in Youtube).
I have read and implemented this tutorial: http://www.strathweb.com/2013/01/asynchronously-streaming-video-with-asp-net -web-api/
But, I want to know if my implementation is the best way? Because my system is very small now, but in the future, I can become bigger to serve more and more customers.
Can someone help me?
Thank you.
>The actual protected access to the file-there is no real http physical access to the file (video), it is stored in the database, or only the IIS application Places that pool users can access (CD/Internal Network/etc.).
> FAKE protects access to files – there is a real http path that allows access to files, but the path is so “weird” and random… found Its probability is so low that users just don’t spend time looking for “other things”… But of course, those who use brute force or other things… After X time, something “pops up” may appear.< /p>
You also pointed out the fact that the “start” is small and becomes larger… This is basically a highly scalable design problem… It all depends on many things… (from vertical or horizontal scaling Start). …Cache, CDN, replication, etc.…..
Other factors: available resources (developers), funds, “machines” (computers/servers), bandwidth/speed, etc.…the number of current users And forecasts for future use… Wait…. I just want to say that sometimes the PRESENT solution is not the FUTURE solution, but it allows you to start making money… And “time” you can use different “resources” to improve it I’ll give you at that time.
With this: The article uses the ASP.NET Web API you pointed to to asynchronously stream videos is a good starting point, it can work, but if you just want to make it fast To achieve, please use the “FAKE PRIVATE” logic first. …. You really don’t need to worry about the “asynchronous streaming” code, because the browser player will do it for you.
I am making a small web application that receives requests from clients and replies to them with video streams.
I have an api such as:
[GET] API/video? ID = {} VIDEOID
Which clients will pass their authorization token in the header to receive video streams from the service (I don’t want people without permission to access protected videos on the service – just Like a private video in Youtube).
I have read and implemented this tutorial: http://www.strathweb.com/2013/01/asynchronously-streaming-video-with-asp-net -web-api/
But, I want to know if my implementation is the best way? Because my system is very small now, but in the future, I can become bigger to serve more and more customers.
Can someone help me?
Thank you.
If you try to provide “private” videos, I believe you can divide the architecture into two basic types:
p>
> Actual protected access to the file-there is no real http physical access to the file (video), it is stored in a database, or a place that only IIS application pool users can access (CD/Internal Network/ Etc.).
> FAKE protects access to files-there is a real http path that allows access to the file, but the path is so “weird” and random… the probability of finding it is so low that the user just Don’t spend time looking for “other things”… But of course, those who use brute force or other things… After X time, something “pops up” may appear.
You also pointed out the “start “The fact that it’s small and getting bigger… This is basically a highly scalable design problem… It all depends on a lot of things… (starting with vertical or horizontal scaling). … Caching, CDN, replication, etc…. .
Other factors: available resources (developers), funds, “machines” (computers/servers), bandwidth/speed, etc….the number of current users and the forecast of future usage…etc… I just want to say that sometimes the PRESENT solution is not the FUTURE solution, but it allows you to start making money… and “time” you can use different “resources” to improve it for you at that time.
With this said: The article uses the ASP.NET Web API you pointed to to stream videos asynchronously is a good starting point, it can work, but if you just want to make a quick implementation, please use the “FAKE PRIVATE” logic first… .You really don’t need to worry about the “asynchronous streaming” code, because the browser player will do it for you.