Dave's megaref suggestion was the kind of thing I had in mind initially but
using Agents might be make more sense.
I'm going to have a play around then report back on my progress. Thanks
for your thoughts, it's very much appreciated.
James
On Friday, 12 April 2013 07:52:22 UTC+1, Cedric
What about a map of table IDs to agents?
The map itself only needs to change if an event creates or destroys a
table. Anything else impacts a single table, and can be sent off to that
table's agent. An agent makes sense to hold each single table, as tables
undergo sequential transformations trigge
On Thursday, April 11, 2013 2:35:03 PM UTC-7, James Adams wrote:
>
>
> How would you do this? All thoughts welcome and appreciated
>
To simplify matters you could think about decoupling the incoming game
events from the state changes; for example, have a queue hold game events
and then serial
have a look at this for a discussion of exactly that question.
http://clj-me.cgrand.net/2011/10/06/a-world-in-a-ref/
https://github.com/cgrand/megaref
On Friday, 12 April 2013 07:35:03 UTC+10, James Adams wrote:
>
> Hi,
>
> I'm new to Clojure and trying to write a multiplayer poker web app.
Hi,
I'm new to Clojure and trying to write a multiplayer poker web app. I'm
looking for advice early on regarding state management.
I'm using aleph and compojure for the communications with actions from
players coming in through compojure on different threads of the netty
server.
When a mess
