-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New signatures to ESP8266WebServer::sendContent #2567
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
Comments
Actually you do not need to specify size when sending if you use you can see how it can be used with template on my project : https://github.com/luc-github/ESP3D/blob/master/esp3d/webinterface.cpp#L214-L394 one send part is here FYR: https://github.com/luc-github/ESP3D/blob/master/esp3d/webinterface.cpp#L379-L392 |
I understand that. I just think it's not necessary duplicate my big |
Sorry I misunderstood the question - but I would say why duplicate ? why not use |
OK. no problem. Just a suggestion. |
@wellrats could you please make a PR with your suggestion? |
Fixes esp8266#2567 Allow the web server to send plain C strings instead of requring they be encapsulated inside a String class object. Saves memory vs. having to convert C strings to Strings (i.e. duplication of data), overloads on the efficient sendContent_P(char*) methods.
Fixes #2567 Allow the web server to send plain C strings instead of requring they be encapsulated inside a String class object. Saves memory vs. having to convert C strings to Strings (i.e. duplication of data), overloads on the efficient sendContent_P(char*) methods.
Hi all,
Would it be possible in next version of this lib insert another signatures for
ESP8266WebServer::sendContent as follow
Useful when parsing a
char*
buffer like a HTML template from a file, and sending little pieces of this buffer to client after parsed. Call<server_instance>.client().write( ... )
directly is not an option, because final length of parsed buffer is unknown and encoding ischunked
Thanks in advance
The implementation.
The text was updated successfully, but these errors were encountered: