- Joined
- Jan 27, 2017
- Messages
- 323
- Reaction score
- 270
Few new updates that do not reflect on the version number of the software:
I noticed that in some cases when the server gets a bad packet it trashes the whole system throwing a <2> error, so I decided to catch this error and put the server back into a waiting state so it can continue. This should help out rectify sudden disconnection errors and make for a more stable platform.
Also I added a clear feature for data logging so it doesn't just endlessly log data to the point where some webapps have a difficult time loading all the data. If the server receives a historical data log every 1000 milliseconds there would be roughly 5 million plus entries along with the rest of the API's data. I will eventually try to figure out how to make something like this work but for now it's a little too much to shovel on-top of the other things going on with SB.
I noticed that in some cases when the server gets a bad packet it trashes the whole system throwing a <2> error, so I decided to catch this error and put the server back into a waiting state so it can continue. This should help out rectify sudden disconnection errors and make for a more stable platform.
Also I added a clear feature for data logging so it doesn't just endlessly log data to the point where some webapps have a difficult time loading all the data. If the server receives a historical data log every 1000 milliseconds there would be roughly 5 million plus entries along with the rest of the API's data. I will eventually try to figure out how to make something like this work but for now it's a little too much to shovel on-top of the other things going on with SB.



