sushant12
This particular file is a behaviour.
https://github.com/phoenixframework/phoenix/blob/v1.3.4/lib/phoenix/transports/serializer.ex#L1
And this is implementing it
Now my question is, Why do I even need to use a behaviour? If I were to do this for the second link ^^ it will still work.
defmodule Phoenix.Transports.V2.WebSocketSerializer do
@moduledoc false
# @behaviour Phoenix.Transports.Serializer
alias Phoenix.Socket.{Reply, Message, Broadcast}
@doc """
Translates a `Phoenix.Socket.Broadcast` into a `Phoenix.Socket.Message`.
"""
def fastlane!(%Broadcast{} = msg) do
data = Poison.encode_to_iodata!([nil, nil, msg.topic, msg.event, msg.payload])
{:socket_push, :text, data}
end
.
.
.
So what’s the point of using behaviour? The Phoenix.Transports.Serializer just defines functions without function body and leaves it to other module to implemente that function’s body.
What am I missing?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
peerreynders
FYI:
Also Liked
Ankhers
You can think of it like a contract that is visibile to the compiler.
Right now the behaviour defines a single function
fastlane!/1. What if, in the future, that behaviour changed and added a new function. You would now havefastlane!/1andfoo/2. The compiler will let you know that you have a module that does not fully comply with the contract that has been written.hauleth
@behaviouris just compiler annotation that helps you when you miss some functions required by the caller, it doesn’t change anything else.MrDoops
The
@behaviourredirects the dependencies allowing for swappable implementations of the interface. This means the Phoenix framework application code can depend on theSerializerbehaviour/interface/contract instead of theWebSocketSerializerdirectly. So if there were a situation where you need a special serializer, you wouldn’t need to fork Phoenix or wait for them to change it. We would just need to implement anotherSerializerand configure Phoenix to use it.Last Post!
sushant12
thanks . You know what links to share