ketupia
Is there the concept of a safe read time for data consistency?
Is there the concept of a safe read time for data consistency?
Suppose you’re careful to place the systems in order in manager.ex so that at the end of any tick the data about the world is consistent. (i.e. no one is still moving despite being out of fuel or targeting a dead enemy.) Reading data while the systems are running might get data that doesn’t make sense. E.g. The monster I attacked previously has been marked dead but my targeting system hasn’t run yet and picked the next monster, so I attack the dead monster again.
Is the idea that the system will be close enough to correct for reading due to the high ticks per second?
- or -
Is it an indication I’ve modelled my data and systems improperly?
First Post!
APB9785
E.g. The monster I attacked previously has been marked dead but my targeting system hasn’t run yet and picked the next monster, so I attack the dead monster again.
Why would you attack again? It should run through the list of all your other systems (including the targeting system) before cycling back around to the attack system.
Is it an indication I’ve modelled my data and systems improperly?
I’m thinking this may be the case, but would have to see more of the code to say for sure.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









