04-29-2021, 05:10 PM
Sounds odd. Since the main difference seems to be that you are using properly threaded code in your non-working example, I could imagine that your code is running too efficient. A thing to know about the web server implementation in phyphox is that it is not multi-threaded. This in particular means that the phyphox web server will not handle any request until the previous connection has been closed. On most simple implementations this is not a problem and typical parallel requests from webbrowsers are patient and wait until their requests are being handled.
So, my first theory would be that your proper implementation sends a request just when the last one has been closed but before the poor phone had the time to open back up for business. Just a first thought, but without aby node.js experience or the code I cannot really say more... On the other hand it is weird that the full requests come through just fine.
So, my first theory would be that your proper implementation sends a request just when the last one has been closed but before the poor phone had the time to open back up for business. Just a first thought, but without aby node.js experience or the code I cannot really say more... On the other hand it is weird that the full requests come through just fine.