Tonight I started the event server that basically serves as the timer for implementing pants shitter. My plan is to use System V IPC message queues to communicate with a daemon that will poll its own in memory database and then update rooms. It is written in C. In the process I'm also learning about syslog and other older UNIX technologies. My rationale is that this keeps the event server portable, performant, and robust. Also I find it very interesting.
So tonight was mostly research, but I do have a daemon running that is writing logs to syslog. I've also added a little todo on the last item; a deployment script so I can easily update and push to a server.
Decision parsing based on traits
Decision submission, resolution parsing from XML, modifying traits
Authoring tools for rooms
XML validator and a test feature
Enter game and exit game (merge traits back to player)
Game invites, declines.
General game rules, like death and pants shitter. <--- IN PROGRESS
Email functionality, day timer <--- IN PROGRESS
Unit testing, code cleanup, documentation, minor aesthetic fixes, deployment
2.5 Hours
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tonight I started the event server that basically serves as the timer for implementing pants shitter. My plan is to use System V IPC message queues to communicate with a daemon that will poll its own in memory database and then update rooms. It is written in C. In the process I'm also learning about syslog and other older UNIX technologies. My rationale is that this keeps the event server portable, performant, and robust. Also I find it very interesting.
So tonight was mostly research, but I do have a daemon running that is writing logs to syslog. I've also added a little todo on the last item; a deployment script so I can easily update and push to a server.
2.5 Hours