News for hackers. Stuff that matters.
Re:The Blink Protocol by wavesounds on Sunday January 20, 2013 @03:35AM (#5086392)
"Blink can be used as an efficient presentation layer on top of middleware solutions like message queues and messaging platforms. However, Blink is also well-suited to be layered on TCP and UDP without any need for encapsulating headers, thanks to its built in message type system."

How is it TCP without the headers? And how can you put a layer on top of TCP and call that saving space? Shouldn't you just be using TCP? It's late I must be missing something ...

Re:The Blink Protocol by ekimekim on Sunday January 20, 2013 @09:50AM (#5087056)
It's a standard for encoding data over streams like TCP. If you recieve "00 4a 33 2b" over TCP, you have no idea what it means. But if you have a codebook or language defined to understand that data, you'll understand it means "Meet me on the first floor in half an hour". Blink is: - A meta-language for defining such languages - A specification of how messages in these languages are turned into binary data and back.

When both client and server know the definitions (written in the meta-language), they can determine which kind of message the other side is using because of the metadata sent with the message (their "message type system") without the need for any extra information, like a HTTP content-type header.