3f0
{"about":"Spark makes using and creating connected devices easy. Learn more and pre-order the Spark Core and accessories at www.spark.io","category":"Computers/technology","description":"Spark makes using and creating connected devices easy. The Spark Core an Arduino-compatible, Wi-Fi enabled development kit pairs with the Spark Cloud powered development platform to make creating internet-connected hardware a breeze now available for pre-order at: https://www.spark.io","is_published":true,"location":{"street":"","city":"Minneapolis","state":"MN","country":"United States","zip":""},"products":"Spark Core, Spark Cloud","talking_about_count":395,"username":"sparkdevices","website":"http://www.spark.io","were_here_count":0,"id":"427120970660412","name":"Spark","link":"http://www.facebook.com/sparkdevices","likes":2381,"cover":{"cover_id":537602636278911,"source":"http://sphotos-f.ak.fbcdn.net/hphotos-ak-prn1/s720x720/923349_537602636278911_656089984_n.jpg","offset_y":40,"offset_x":0}}
0
Yes that looks complete! What is that 0 or the 3f0 at the beginning?.. heck if I know. BTW I have a cool project with all of this code in mind⌠coming soon.
The server is sending keep-alive connection data in pieces (Transfer-Encoding: chunked) and that ârandomâ stuff is actually hexadecimal size of the next piece.
3f0 is 1008 in decimal and 0 means there is no more data coming this time.
Aha⌠makes sense⌠1008 characters there. Except shouldnât that be in the header as Content-Length: 1008 ? When I use Advanced Rest Client I see content-length: 574
Coffeeâs code looked for "\r\n\r\n" to indicate the body. Is the first line of the body always the content length? I guess if so, we have an easy way to look for the end of the data, and we can close the socket ourselves.
Yeah, we are not really parsing the headers to understand how to read the data and handle the connection. I guess I have to go dig up some of my old HTTP browser code to see if I can âborrowâ from there.
HTTP Requests are quite annoying sometimes, because there is easy way to just parse the body you get with minumum headers sent and the harder way to make it work properly according the headers and stuff. With your own custom client you most of time get along with the easier one.
In this case, the trick to get Content-Length from Facebook is to add one more header âAccept-Encoding: deflate, compressâ. Some servers seem to give you the content length without it.
Here is a link where you can check things. Easiest way is to use a proper client, check what headers it sends and receives and try to adapt your code to that. http://www.w3.org/Protocols/rfc2616/rfc2616.html
www.hurl.it is one of online request makers I have used lately, mainly because the short and easy url.
Ah, I see now. Thanks @weakset. The smaller content-length was due to it being compressed, and the additional headers request the data to be sent uncompressed. I see content-length of 1008 now in Advanced Rest Client, and also Hurl.it (cool site!).
Itâs weird, just adding the âAccept-Encoding:â header with no value will decompress it⌠or you can force it to compress with âAccept-Encoding: gzipâ.
In the case of the CC3000, it must be decompressing by default or we wouldnât be able to read the characters. I wonder if thatâs an automatic header sent, or just something it does if it sees compressed data.
Also to note, it is faster to receive compressed data, as long as you can uncompress it faster than sending it uncompressed. Probably a wash for small data packets.
