-
The server should be doing all of the work, while the Client is just a front-end, rendering everything received from the server, and firing calls to do things. Client should query available servers on…
-
- [ ] aggiornare i tags
- [ ] rimuovere Cos'è
-
![v5](https://cloud.githubusercontent.com/assets/384189/2740142/2b27fc44-c6ca-11e3-9b27-299b18654f6d.jpg)
update server architecture to be similar to this, by splitting into these processes hopefully …
-
**Is your feature request related to a problem? Please describe.**
It's a bit annoying to need to worry about the security implications of exposing every server function when some functions should be…
-
-
I'm moving the discussion about architecture from #27 to here.
The idea is to have multiple services which are handling different aspects of the game functionality like game logic, authentication, ra…
Noir- updated
7 years ago
-
I _think_ this project already follows this, but just want to confirm, and if not raise this as an issue.
I would love to see an approach taken by VS Code, where server and client are decoupled. Th…
-
Create a droplet on Digital Ocean that auto-deploys from a GitHub Webhook.
-
Student is the client, teacher hosts the server. Limits students ability to modify file
-
The client and server should be separate models.
- In single player mode the client starts the server as subprocess.
- Server is always authorative and holds the state of the game, the client only…