Timeline for Making server logic independent of client interaction
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2014 at 0:49 | vote | accept | laggingreflex | ||
| Jun 20, 2014 at 0:04 | answer | added | Emw | timeline score: 1 | |
| Apr 21, 2014 at 15:46 | comment | added | Dunk | The logic needs to run in a separate thread that handles client requests. Put client requests from your socket.on method into a message queue and your server chooses when to process the message(s). You'll probably need to keep that client socket open to have the server send a response at its time of choosing. The reason for that is that some networks will block connections initiated from the outside unless those connections are opened by the network admin. So, you probably won't see this on your LAN, but if you move to a WAN that's when your design may need a rewrite without considering this. | |
| Apr 20, 2014 at 22:40 | review | Close votes | |||
| May 11, 2014 at 20:06 | |||||
| Mar 17, 2014 at 12:19 | answer | added | Asons | timeline score: 0 | |
| Mar 17, 2014 at 11:28 | history | asked | laggingreflex | CC BY-SA 3.0 |