Updates of what's happening

[matjack1]

Hey dear community!

Sometimes it looks like nothing is happening on esp-rfid land, and it might be true, but sometimes we are working on something that takes multiple days to see the (PR) light.

Since I'm happy that I'm progressing on a long-standing issue, but I'm a bit frustrated that I cannot open a PR yet, I'm trying this experiment to share what's going on.

I've spent quite some time trying to understand where the web-UI intermittent errors were coming from. I'm talking about these issues, for example: #311, #442 or #388.

I have learned a bit more about debugging and found all the times a different stack trace. I was stuck. Then I realized that the problem was similar to the MQTT queue processing problem. When a websocket response was taking a bit longer, for example accessing the file system, the ESP timers for network/pin related matters were firing and sometimes they were touching the same memory handled by the socke response and everything was crashing.

So the solution that I'm implementing is the same as the MQTT one: add the message to a queue and process it in the loop. While at it I'm also changing stuff in order to reply only to the client making the requests, so it should support multiple browsers.

From the early tests I've done it looks very robust now, but I need to finish some stuff :) That's why I'm writing this here, to share my progress!

I hope to share very soon a PR ;)