Open christoph-v opened 5 years ago
Client commands are handled in in app.js. Server commands are handled in pc.multiplayer/public/javascripts/player.js
fyi: John has not only added to https://github.com/christoph-v/spark/tree/master/3rd-party-input/yottzumm%40gmail.com , but also done a review of the protocol's brainstorming at https://github.com/christoph-v/spark/tree/master/3rd-party-input/esdp-bs
Currently analysing the file app.js at https://github.com/coderextreme/pc.multiplayer. First insight: pc.multiplayer doesn't use the plain http module of node.js, but it uses socket.io for low-layer networking. My intention was to use AJAX/fetch() for client driven communication and SSE for server driven communication. Interesting challenge.
Next chunk to be analysed/digested: https://www.digitalocean.com/community/tutorials/nodejs-server-sent-events-build-realtime-app
Is your feature request related to a problem? Please describe. Tuesday, March 26th 2019, John. C. sent some input for our project. I felt free to store the e-mail in a text file at directory spark/3rd-party-input/yottzumm@gmail.com. However, that input should be analysed, which is some work.
Describe the solution you'd like If somebody likes, please feel free to analyse that input and report related results here at the project. Thanks :-)
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.