FLV Streaming Media plug-in based on trafficserver implementation

After more than a week ago on GitHub posted on the Trafficserver-based MP4 streaming plug-in, the two days just again the FLV streaming plug-in, compared to the MP4 file, the processing of FLV is much simpler, in the jump only need to put the file before and after stitching into a new file output.

Have seen Nginx official FLV plugin implementation, which is based on the offset of the jump, there is no practical reference value, because such as Youku video site in the FLV format video is based on time to jump. The FLV plugin code address based on the Trafficserver implementation is as follows:

https://github.com/portl4t/ts-flv

When you visit an FLV video, the video's jump is reflected by the start parameter in the request URL, such as http://192.168.131.128:8080/kenshin.flv?start= 195.62 this request represents starting from 195.62 seconds and can be experienced by the client tools such as Flash, VLC, mplayer, etc.

The follow-up will continue to refine the code and documentation for this project on GitHub, and you are welcome to use it.

FLV Streaming Media plug-in based on trafficserver implementation