Qqwy
TypeCheck Core Team
Hey everyone!
Some of you might know that we are working on a chat application. (The initial beta version will soon be released! Wooh!)
How it has been set up, is that the main chat server only has as goal to communicate with clients running in the user’s browser. This chat server itself does not do any HTML rendering (the front-end rendering code is on other people’s servers), and so will, besides sending one or two static JS files, only communicate using Phoenix Channels.
So I was wondering: Are there parts of Phoenix that can be turned off, or configured in such a way that it works extra well for channel-based communication?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sribe
Bah, I wrote the below thinking you were only using websockets–obviously you can’t drop Phoenix altogether and still use Phoenix Channels.
You could probably just drop Phoenix altogether and use Plug. I personally wouldn’t, because somewhere down the line you’re going to discover that in fact you don’t want a pure channels application. You’re going to want to respond to some plain HTTP requests: /healthcheck, /ready, /ping, etc. You might even want to serve some HTML: /admin/…
chrismccord
Nope
Channel transport connections are intercepted at the top of the endpoint, thus bypassing your plug pipeline, so there’s nothing to optimize. Even if you later decide to serve up other http requests, there won’t be a concern for such features impacting your channel performance.
Qqwy
I just want to say: What an amazing piece of engineering have you built, Chris!