jarvism

jarvism

Hello, everyone!
I am having a really hard time wrapping my head around this one for some reason.
I want to get a token, store it in memory in a module, have it available for all the functions in the module, and update it when the token expires.
In other languages, I might do something like:

token = nil

def handle_token() do
  # Check if I already have a token
  if token do
    # If so, use it.
    token
  else
    # If not (or if it's expired), get a new one.
    token = Req.get(www.token.com)
  end
end

This is obviously oversimplified, but I think you can understand what I mean. What is the idiomatically correct way to do this in Elixir?
I have looked into using ETS for this, but it seems like a lot.

I look forward to your feedback, and thank you!

Showing Posts 1 to 4

dimitarvp

dimitarvp

Simply put, you don’t do that in an FP language (though there are escape hatches like ETS indeed).

You’ll get better responses if you specify your original problem – and not how you want to solve it.

gpopides

gpopides

Are you looking how you can handle state? If yes you can use Agents for storing something simple (a string)

As mentioned, you cant do what you are trying because modules are not classes, they don’t contain state.

For that you need a GenServer (which agent is just more simplified)

hlx

hlx

A GenServer would be perfect for that. You can even make it so that the GenServer automatically refreshes the token every interval.

e.g.

defmodule TokenManager do
  use GenServer
  
  # Stick `TokenManager` in your Application's children
  def start_link(init_arg) do
    GenServer.start_link(__MODULE__, init_arg, name: __MODULE__)
  end
  
  def token do
    GenServer.call(__MODULE__, :token)
  end
  
  def init(init_arg) do
    token = 1
    Process.send_after(self(), :refresh_token, :timer.seconds(2))
    {:ok, token}
  end
  
  def handle_call(:token, _from, token) do
    {:reply, token, token}
  end
  
  def handle_info(:refresh_token, old_token) do
    new_token = old_token + 1
    Process.send_after(self(), :refresh_token, :timer.seconds(2))
    {:noreply, new_token}
  end
end

Edit: untested code FYI

masudme09

masudme09

For a similar case, when I need to use and update something, I use the following kinda programming pattern. But as @hlx mentioned, Genserver might serve best for your case without further knowing the context of your original problem.

defmodule SomeModule do
@state %{token: nil}

def some_function(params, state) do
 state
end

def another_function(params, params2, state) do
state
end

def update_token(state) do
# update the token
%{token: updated_token}
end

end

So, I try to pass around states, between functions, so any update that happens in any function should be available to the next one. Not sure it serves your purpose, maybe you can add further context to it.

— 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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
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
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
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews