We already have discussed two possible technologies running the platform on the server:
- Erlang
- Akka / Scala
Actually, both approaches are very similar since we need to call an agent on a "remote" machine (sandboxed virtual box), give it a piece of code at wait for the results of the execution. It is possible to have many such agents open in parallel - one per open game session / task execution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- view is the JS client
- controller is just a dispatcher on server, redirecting everything to sandboxes
- model is the sandbox where the game session is also stored and managed - why don'w we also use them for managing the game session and such?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll check it out in my experimental environment. As soon as it works, we can reduce the initial scope to the JVM languages and start building the thin foundation Linux for the KVMs (sandbox).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We already have discussed two possible technologies running the platform on the server:
- Erlang
- Akka / Scala
Actually, both approaches are very similar since we need to call an agent on a "remote" machine (sandboxed virtual box), give it a piece of code at wait for the results of the execution. It is possible to have many such agents open in parallel - one per open game session / task execution.
a half-classic MVC:
- view is the JS client
- controller is just a dispatcher on server, redirecting everything to sandboxes
- model is the sandbox where the game session is also stored and managed - why don'w we also use them for managing the game session and such?
Here is the sample provided by Jonas Bonér on how to use the Akka RemoteActor in our case:
http://github.com/jboner/akka/tree/master/akka-samples/akka-sample-remote/
I'll check it out in my experimental environment. As soon as it works, we can reduce the initial scope to the JVM languages and start building the thin foundation Linux for the KVMs (sandbox).
Works for me. But the README is wrong: You need to call 'update' before 'console'. And replace 'update' with 'import sample.remote._'.