Timeline for How to make better looking webpages on an Arduino webserver?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2022 at 17:31 | history | edited | ocrdu | CC BY-SA 4.0 |
added 2 characters in body
|
| Dec 10, 2021 at 0:15 | history | edited | ocrdu | CC BY-SA 4.0 |
added 123 characters in body
|
| Dec 8, 2021 at 16:49 | history | edited | ocrdu | CC BY-SA 4.0 |
added 83 characters in body
|
| Dec 8, 2021 at 16:35 | history | edited | ocrdu | CC BY-SA 4.0 |
added 11 characters in body
|
| Dec 8, 2021 at 16:33 | comment | added | ocrdu | @EdgarBonet: I know, but using base64 encoding makes it easier to copy/paste the contents of a file into the code without breaking it because of the control characters etc. in the gzip-ed file. I had enough memory, so I didn't go the more efficient way of escaping the problematic characters in the gzip output and use that. I will admit to some laziness here. | |
| Dec 8, 2021 at 10:44 | comment | added | Edgar Bonet | This is an interesting approach, but I do not see the usefulness in using base64 encoding. It makes your document consume 33% more memory, then you allocate the original size on the stack in order to decode it (at which point it occupies 233% of its size), and you need the extra code for decoding. It would be more efficient to store the gzipped page unencoded, as an array of bytes (not a C string). | |
| Dec 8, 2021 at 9:58 | history | answered | ocrdu | CC BY-SA 4.0 |