mazzie

mazzie

I am new to Phoenix. I was wondering if it is possible to create topics dynamically in Phoenix.
From what I understood till now in Phoenix if a user joins a topic they get all the messages sent on that topic. What if I want add a functionality in which user can create own topic and then send messages on it. Is that possible ?

Showing Posts 1 to 8

James-Byrne

James-Byrne

Thats totally possible, so in the user_socket.ex file you add a room as "room:name:*". Just add whatever you want after the star when joining the channel and boom your off.

For example I have a team channel defined like :

channel("team:*", TpPhoenixWeb.RequestCounterChannel)

The user then joins a channel named "team:API_KEY_HERE" and only they can see what is broadcast there.

mazzie

mazzie OP

But can these topics be created on the go. As in without being written in user_socket.ex in the start ?

zinclozenge

zinclozenge

You would need a macro that dynamically creates user_socket.ex based on input provided to the macro.

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

To be clear, what the macros in user_socket do is route topics that have a particular prefix to a particular channel module. You could make a generic one:

channel "generic:*", GenericChannel

Then you can put literally anything after generic:

axelson

axelson

Scenic Core Team

I believe that you can meaningfully accomplish this task without creating a macro as specified by @benwilson512 above. And in general if you can accomplish something with just modules and functions then use that approach. Quoth the Elixir docs: “Macros should only be used as a last resort”.

zinclozenge

zinclozenge

Yes, I think that whatever use case the OP has should be covered by using the method provided by @benwilson512.

rm-rf-etc

rm-rf-etc

How do we join multiple topics in phoenix.js? Looking at the source, I see it supports only 1 topic per channel, while the docs states, “the client may join any number of topics on any number of channels”.

axelson

axelson

Scenic Core Team

Joining multiple topics can be accomplished by calling socket.join multiple times, this will create multiple channels multiplexed over the same socket. Here’s an example:

let socket = new Socket("/socket", {params: {userToken: "123"}})
socket.connect()

let channel1 = socket.channel("room:123", {token: roomToken})

channel1.join()
  .receive("ok", ({messages}) => console.log("catching up", messages) )
  .receive("error", ({reason}) => console.log("failed join", reason) )
  .receive("timeout", () => console.log("Networking issue. Still waiting..."))

let channel2 = socket.channel("room:456", {token: roomToken})

channel2.join()
  .receive("ok", ({messages}) => console.log("catching up", messages) )
  .receive("error", ({reason}) => console.log("failed join", reason) )
  .receive("timeout", () => console.log("Networking issue. Still waiting..."))

Since joining multiple topics as a client is a different topic than creating dynamic topics as the server, if you still have questions it’s probably better to continue the discussion in a separate post.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
RemyXRenard
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
nseaSeb
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
velrest
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
samoloth
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
FlyingNoodle
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
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews