Looking at the code, part of the problem seems to be that it returns 0 for
success and -1 for failure, rather than the number of bytes read (which is what
EthernetClient does)
However, trying to amend the WiFiClient code to return the number of bytes also
didn't fix the issue. I haven't had chance to dig into it further yet.
Original issue reported on code.google.com by adrian.m...@gmail.com on 3 Sep 2012 at 5:23
Original issue reported on code.google.com by
adrian.m...@gmail.com
on 3 Sep 2012 at 5:23