axelson
Scenic Core Team
ElixirConf 2017 - HTTP 2 Plug to Phoenix Cowboy too - @Gazler
In this talk, we will look at the changes in Cowboy 2 and how we can use it with Plug and Phoenix by using a custom Plug adapter. We will look at how this can be done using a library and integrating it with Plug. The same technique will be applied to Phoenix, writing a custom handler in a library and using it with Phoenix.
We will also explore how HTTP/2 can be used to build a new Phoenix Transport, allowing Phoenix PubSub to work with a bidirectional HTTP/2 channel. We will investigate how existing transports work, and what changes are required to implement a custom transport.
Audience: Intermediate-Advanced
All talks are available in the Elixir Conf 2017 Talks List or via the elixirconf2017 tag
Trending in Talks
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
JEG2
This talk is quite technical and seems to hint at great things to come. It’s probably not a huge draw for most people working at higher levels though.
axelson
Definitely a more low-level talk. I also wanted to point out that the actual video is only 43 minutes, there’s about 15 minutes of a black screen at the end of the video.
I’m not sure what the best way to integrate server push with Phoenix templates would be. Adding server push directly to
static_pathis of course asking for trouble. Easiest is probably to add server push url’s to theconn(or a field on the conn), but that might not be the nicest API since they could easily get out of sync.Since phoenix templates are really just io lists, perhaps we could have special elements in the list that will render into the HTML as the static path, but will also define a path that will be server-pushed.