This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Possible bug with multiple fetch?
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.

Messages In This Thread
Possible bug with multiple fetch? - by kwikman - 04-29-2021, 04:25 PM
RE: Possible bug with multiple fetch? - by Sebastian Staacks - 04-29-2021, 05:10 PM

Forum Jump: