#Node.js convert octet stream to json how to
#Node.js convert octet stream to json code

UTF-8 states that characters should be encoded in bytes. One of the definitions for Character Encoding is the UTF-8. Specifically, how many bits to use to represent the number. Just as there are rules that define what number should represent a character, there are also rules that define how that number should be represented in binaries. You might think, well, just convert 76 to the base-2 numeral system. Now, the computer will, in turn, represent the number 76 to its binary representation. So weРІР‚в„ўve seen how computers represent characters in numbers. In fact, it is the Unicode in your browser that states that 76 should represent L. JavaScript plays really well with Unicode Character Sets. We have different definitions of these rules.The very popular ones include Unicode and ASCII. But how does a computer know what exact number will represent each character? How does it know to use the number 76 to represent L? Character SetsР”В¬haracter Sets are already defined rules of what exact number represents each character.

#Node.js convert octet stream to json code

What did you see? The number 76? That is the number representation or Character Code or Code Point of the character L. Open your browser console and paste the following code snippet and then hit enter: 'L'.charCodeAt(0). So for the string РІР‚СљLРІР‚Сњ, computers will first convert L to a number that represents L. How will a computer represent the string РІР‚СљLРІР‚Сњ in binaries? To store any character in binaries, Computers will first convert that character to a number, then convert that number to its binary representation.

#Node.js convert octet stream to json how to

Computers know how to represent all types of data in binaries. We also have strings, images, and even videos. Computers understand that math.Р”В«ut numbers are not the only data type we work with. ItРІР‚в„ўs the simple binary numeral system we learned in basic math - expressing a number in the base-2 numeral system.

How does a computer know how to do this conversion? Well, itРІР‚в„ўs pure math. For example, to store the number 12, a computer needs to convert 12 to its binary representation which is 1100. To store or represent a piece of data, a computer needs to convert that data to its binary representation. For example, the following are five different binaries, five different sets of 1s and 0s:Р”В®ach number in a binary, each 1 and 0 in a set are called a Bit, which is a short form of Binary digIT. Binary is simply a set or a collection of 1s and 0s. You probably already know that computers store and represent data in binaries. Well, letРІР‚в„ўs try to tackle these big words from the last to the first.

Now thatРІР‚в„ўs simpler right? ButРІР‚В¦ Buffer, streams, binary dataРІР‚В¦ still many big words. The Buffer class was introduced as part of the Node.js API to make it possible to manipulate or interact with streams of binary data. Extracting from that introduction, we could safely say: LetРІР‚в„ўs try to simplify that a bit by rephrasing it, so we can have a clear focus and not be distracted by the many bells and whistles in there. Hmmm, unless you had prior knowledge of all the words in the above sentences, they are probably just a bunch of jargon. The Buffer class was introduced as part of the Node.js API to make it possible to interact with octet streams in the context of things like TCP streams and file system operations. When introducing Buffer, the official Node.js docs states in partРІР‚В¦ РІР‚В¦ mechanism for reading or manipulating streams of binary data.

And thatРІР‚в„ўs exactly why IРІР‚в„ўm writing this piece - to help us demystify some of these features and take our Node.js learning to the next level. However, if mysteries get you really curious, and youРІР‚в„ўll stop at nothing to satisfy your curiosity, and if you want to take your Node.js understanding to the next level, then you really want to dig deeper to understand the many core features of Node.js, like Buffer, for example. Well, true, you might never work with them directly if you chose to remain an average Node.js developer. And some will brazenly tell you that you donРІР‚в„ўt need to understand them because you might never work with them directly. Sadly, many tutorials and books will jump straight to teaching how to develop web applications with Node.js packages without letting you understand the core features of Node.js and why they exist. Indeed, those words could be very intimidating, especially when youРІР‚в„ўre coming into web development with Node.js without any CS degrees. Are you always mystified, like me, whenever you come across words like Buffer, Stream, and binary data in Node.js? Does that feeling make you shrink from understanding them, thinking they are not meant for you but only for Node.js gurus and package developers to understand?