mbed official WiflyInterface (interface for Roving Networks Wifly modules)
Dependents:
Wifly_HelloWorld
Websocket_Wifly_HelloWorld
RPC_Wifly_HelloWorld
HTTPClient_Wifly_HelloWorld
... more
2 comments:
Hi Henry, I'm far from an expert, but was also looking for a non-blocking version. What I found is that Socket has a 'set_blocking(...)' API, but setting it to false didn't make it non-blocking. I followed that for a while, but didn't get to a solution. And then in looking at your suggestion, I have to wonder if it is possible that one call to this might end up getting "*OP" and the next call picking up "EN*" - which then wouldn't match. In some code I was working with, the fragmentation happened a few characters into a subsequent line, so I had to cache those from call to call.
Yes, you are right, I have experienced this Problem already. Maybe an increase of the cyclic receive buffer (which is large enough to capture a Connection request) is sufficient ? Of course one would should not call any other wifly functionality between two accept calls in this case.
Unfortunately the RTOS library is not working together with the WiflyInterface. If it would there would be no need for a non-blocking Version for me anymore.
Hi Henry, I'm far from an expert, but was also looking for a non-blocking version. What I found is that Socket has a 'set_blocking(...)' API, but setting it to false didn't make it non-blocking. I followed that for a while, but didn't get to a solution. And then in looking at your suggestion, I have to wonder if it is possible that one call to this might end up getting "*OP" and the next call picking up "EN*" - which then wouldn't match. In some code I was working with, the fragmentation happened a few characters into a subsequent line, so I had to cache those from call to call.