-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*CLOS* in the output #20
Comments
ghost
assigned harlequin-tech
Apr 4, 2013
Thanks for the bug report. I'll try out your fix and see if I can fix the connected flag status. |
It won't fix the connected flag. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I try to make subsequent calls to retrieve multiple files from a server.
The flag "connected" is unreliable. In the first call, it's true. In the second, after "open" it's true, then suddenly it's false.
Because this flag is incorrect, when I download a file and save it on the SD card, it's 6 bytes longer because of the added "CLOS" phrase inside of the WiFly stream.
The main problem is in the function "available":
int WiFly::available()
{
int count;
}
I modified it to always check for the "CLOS" statement, connected or not, and now files are correct.
int WiFly::available()
{
int count;
}
The text was updated successfully, but these errors were encountered: