Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 22 lines (10 sloc) 1.081 kB
ed50407 Added TODO list.
Torben Hoffmann authored
1 # To-Dos for Chronos
2
3
4 ## Removal of timers for terminating requesters
5
6 When the requester of a timer dies it should be possible to get the timers that has been requested removed.
7
8 This is only a problem if more processes share the same Chronos timer server, since a single process which has started a Chronos timer serevr will drag Chronos down with it when it dies.
9
10
11 ## Flexible linking to the creating process
12
13 Right now a Chronos timer server can only be started with `start_link/1` which means that it will die when the creator of it dies.
14
15 It might be a good thing to decouple this, but since I have not found a good use case for this yet it is not implemented.
16
17 ## Support for recurring timers
18
19 If you want to have a recurring timer, say every 5 seconds, you have to start a new timer every time it expires.
20
21 If this is too troublesome to do it will be possible to introduce recurring timers - I encourage users of Chronos to try it out as it is today and provide me with some information about how recurring timers should work for them. Then I will implement the feature.
Something went wrong with that request. Please try again.