-
Notifications
You must be signed in to change notification settings - Fork 73
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
Some things should be printed immediately #8
Comments
We might be able to re-use the header processing from here: https://github.com/ovidiucp/TinyWebServer/blob/master/TinyWebServer.cpp#L99 (Or at least use the technique of storing the headers in some intermediate structure, rather than having to parse them as they arrive in the stream). |
We might also be able to use a different status code, which could be easier to parse than a proper HTTP header... |
I've been thinking a bit more about this. I'm relatively sure that there's no way to fit in decent header processing into the space we have left on the Ardunio, principally because the headers could arrive in any order from the server. However, the server could supply a single, custom header that included a more easily parseable set of values. For example:
The server returns the interesting headers as normal, but also provides a single, encoded header which has a value that can be more easily broken down: Using a single header makes the Arduino software much simpler. |
This relates to #8, and explores using a single encoded header to simplify parsing of more complex parameters from the server.
If you were using a printer to send a message, you might want it to appear without intervention by the recipient.
I think we might be able to do this elegantly using HTTP headers (e.g.
X-Print: now
).The text was updated successfully, but these errors were encountered: