From 46cf95a2ad3170fd0694458b7d68b83a11f62dd7 Mon Sep 17 00:00:00 2001 From: Grant Henke Date: Thu, 10 Mar 2016 11:57:21 -0600 Subject: [PATCH] MINOR: Add header and footer to protocol docs Because protocol.html is going to be in its own page it needs the header and footer included. --- docs/protocol.html | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/docs/protocol.html b/docs/protocol.html index 98923aad53405..cb359f17f6d70 100644 --- a/docs/protocol.html +++ b/docs/protocol.html @@ -1,3 +1,22 @@ + + + +

Kafka Wire Protocol

This document covers the wire protocol implemented in Kafka. It is meant to give a readable guide to the protocol that covers the available requests, their binary format, and the proper way to make use of them to implement a client. This document assumes you understand the basic design and terminology described here

@@ -160,4 +179,4 @@

Some Common Philosop

A final question is why we don't use a system like Protocol Buffers or Thrift to define our request messages. These packages excel at helping you to managing lots and lots of serialized messages. However we have only a few messages. Support across languages is somewhat spotty (depending on the package). Finally the mapping between binary log format and wire protocol is something we manage somewhat carefully and this would not be possible with these systems. Finally we prefer the style of versioning APIs explicitly and checking this to inferring new values as nulls as it allows more nuanced control of compatibility.

- +