Repository navigation
Support for timers #2
Description
Goal
Execute scheduled functions
Discussion
- Do we want this? With systems like appscheduler or kubernetes cron jobs
- Maybe we can defer the discussion for later
Ideas
1. Decorator
from dam import send, timer
@timer(ms=20)
async def hello():
send("a-topic", {"name": "jon"}2. Add them in a list
This would follow a similar approach to routes
from dam import Timer, App
from .myapp import hello
timers = [
Timer(hello, ms=20)
]
App(timers=timers)Reacted by Marcos Schroh
Activity
marcosschroh commentedon Feb 4, 2020
Option 1 seems maybe more pythonic way, but what I like about option 2 is that we can have a central place where we can see all timers registered at the moment. Shall we go for option 2?
woile commentedon Feb 4, 2020
The thing with a timer list is that you have them in the same place, it's easy to track, and follows the same approach as
Topic. Otherwise you may have them spread in various places.Also approach 1 is the inverse implementation of what we currently have:
everything sinks (topics, confs?? timers??) into the app (like django)
if we use a decorator it would be the reverse approach.
app should receive the stuff and store it somewhere for the decorator to be consumed (like flask)
So I think we should go for approach 2 as well.
But of course way into the future this feature, if we ever need it.