TCPServer with Multiple Clients
Posted: Sat Apr 18, 2015 8:56 pmHi,
I've manage to do a TCP server using WifiServer default ESP8266 library using standard Arduino code.
But I wish to have multiple clients ! I will have to manage multi-threading or pseudo-thread, I'm not afraid about that.
But the WifiServer.available() seems to returning me always the oldest client, although it has been already returned, and the second client succeeded to connect, but still standby. According to what I understood from the library sources, it should first return the first connection, then return the second connection stacked as "_unclaimed", and if no new connections are available/stacked, it should return NULL, Right ? ... But the code will instead will simply return again the first connection for every call to WifiServer.available(). There no reference count or so ever ... That seems a bug to me ... right ?
(there is some related bugs on Arduino side, see http://forum.arduino.cc/index.php?topic=207128.0, but I don't care much about Yun if we got it fixed in our own ESP libs
)
I've manage to do a TCP server using WifiServer default ESP8266 library using standard Arduino code.
But I wish to have multiple clients ! I will have to manage multi-threading or pseudo-thread, I'm not afraid about that.
But the WifiServer.available() seems to returning me always the oldest client, although it has been already returned, and the second client succeeded to connect, but still standby. According to what I understood from the library sources, it should first return the first connection, then return the second connection stacked as "_unclaimed", and if no new connections are available/stacked, it should return NULL, Right ? ... But the code will instead will simply return again the first connection for every call to WifiServer.available(). There no reference count or so ever ... That seems a bug to me ... right ?
(there is some related bugs on Arduino side, see http://forum.arduino.cc/index.php?topic=207128.0, but I don't care much about Yun if we got it fixed in our own ESP libs
)