https://github.com/takusemba/quicplayer
media player using QUIC protocol
https://github.com/takusemba/quicplayer
cronet exoplayer quic
Last synced: over 1 year ago
JSON representation
media player using QUIC protocol
- Host: GitHub
- URL: https://github.com/takusemba/quicplayer
- Owner: TakuSemba
- License: apache-2.0
- Created: 2018-09-27T11:04:08.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-09-28T05:36:18.000Z (almost 8 years ago)
- Last Synced: 2025-04-01T14:14:44.894Z (over 1 year ago)
- Topics: cronet, exoplayer, quic
- Language: Kotlin
- Homepage:
- Size: 1.7 MB
- Stars: 17
- Watchers: 3
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# What's QUIC
QUIC (Quick UDP Internet Connections) is a new transport protocol for the internet, developed by Google.
QUIC is very similar to TCP+TLS+HTTP2, but implemented on top of UDP and has some cool features that TCP+TLS+HTTP2 does not have.
You can find more information about QUIC [here](https://www.chromium.org/quic).
This player is based off of [ExoPlayer](https://github.com/google/ExoPlayer) using QUIC extension.
# Quicstart
You would probably ready to send QUIC request, but the endpoint might not be able to handle QUIC requests.
The esiest way to build an server for QUIC so far is to use [Caddy](https://github.com/mholt/caddy). This is an open-source web server and has an Experimental QUIC support.
Caddy can be an proxy server, so you can just enable QUIC with `-quic` option and proxy your request to your existing web server.
```
https://proxy.example.com {
proxy / http://example.com {
header_upstream Host {host}
header_upstream X-Forwarded-For {remote}
}
tls postmaster@example.com
}
```
For more information, you should check [here](https://github.com/mholt/caddy/wiki/QUIC)
# Others
Slide: [request in a QUIC way](https://speakerdeck.com/takusemba/request-in-a-quic-way-at-shibuya-dot-apk-number-28)