aaco / bwreportingapplication Goto Github PK

Scheduling didn't seem to trigger properly, debug it.

Allow Host name in server host field, currently only accepts IPs.

Improve runtime table creation, right now it does not properly handle foreign keys (would blow up on MIA tables right now anyways), and doesn't handle either multiple keys on one column or one key across multiple columns.

Once #7 is fixed, preserve running states on save.

Right now the code is pretty confusing, once all the feature shit is done, go through, refactor, comment, and get this shit code reviewed.

• Document and format code
• Get code reviewed

Can not properly stop/start the reporter, look into this.

Reporting process dies due to MySql error:
MySql.Data.MySqlClient.MySqlException (0x80004005): Fatal error encountered during command execution. ---> MySql.Data.MySqlClient.MySqlException (0x80004005): Fatal error encountered attempting to read the resultset. ---> MySql.Data.MySqlClient.MySqlException (0x80004005): Reading from the stream has failed. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Validate/create database schema. Relying on manual set up is no bueno

Reporting status indicator only is correct when the reporting thread is running, and not waiting to poll.

• Remove player to session
• Change Player-To-Session-To-Mission-To-Session to just Player-To-Mission-To-Session
• Only write to MySQL on mission complete (or server crash), otherwise track in memory

This should significantly reduce network traffic, and increase reporting run speed. It does make the final mission write a lot more valuable, so ensure it gets written (use repeat logic on failure).

Add better MySQL error handling, recently some hiccup in response time to the MySQL server caused the reporting process to crash while getting or creating a mission session, it should just retry and log the error.

Add player to session to mission to session tracking. Will allow more drill down on player tracking, and give an accurate count of people who played a mission.

Fix issue with blank player being added, probably an issue with joining/loading players. Just filter for blank user names.

Player count received from the bit response is wrong, do a true calculation from the numbers of players connected.

Right now the scheduling system is super ghetto, do better. Might fix #4.

Changes to the web side of the application broke how the application is tracking missions.