Gothic Alpha: Difference between revisions
Adamcolton (talk | contribs) No edit summary |
Adamcolton (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
I think for this, I will start with [https://capnproto.org/index.html Capn Proto]. Pair that with and Entity system. The Entity interface just needs to return an ID. | I think for this, I will start with [https://capnproto.org/index.html Capn Proto]. Pair that with and Entity system. The Entity interface just needs to return an ID. | ||
The other option would be protocol buffers. On the server, I can extend them by embedding. | |||
=== Indexing === | |||
One of the big challenges is indexing. I think the right approach is not do it right away, but see what comes up. | |||
== JS == | == JS == | ||
Revision as of 20:07, 29 December 2015
Laying the ground work for Gothic.
The goal here is to get something that works, but maybe not everything I want.
Objects
This is the core of the whole thing. I want a simple way to have objects on the server be stored or sent to the client.
I think for this, I will start with Capn Proto. Pair that with and Entity system. The Entity interface just needs to return an ID.
The other option would be protocol buffers. On the server, I can extend them by embedding.
Indexing
One of the big challenges is indexing. I think the right approach is not do it right away, but see what comes up.
JS
I need to support as much JS integration as possible. Objects should be automatically exported, so that the only JS work is adding front-end features.
I'll probably use some Lapiz here too - the event system work well with websockets.
I may also pull in GopherJS, but that needs a little further exploration.