You are reading a single comment by @JumJum and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@JumJum
@Gordon is right, I used the HTTP server to get headers parsed.
BTW, is there an easy way to encode/decode socket frames ? Socket itself delivers raw data and I had to seperate the data part oit of it.
I don't know how node.js handles this, but can imagine that code for this already exists somewhere around http handling. (sorry lack of C-handling, tried to find and failed.
May be we could have an option to switch on/off decoding/encoding ?
To be honest, even this short sha1 takes a lot of memory, at least at runtime.
Had to use some "optimization" to get it running. And it takes some time to calculate.
Therefore I would prefer to have sha1 in firmware, same way we have sha224 and sha256.
And if there is a nicer way to do encode64, please give me a hint.