the implementation made a wrong assumption that cookies could be identified only by their name. The RFC states that the tuple of <name, domain, path> is the unique identifier. When more than one cookie has the same name, the map will hold that lost one to be parsed and any previously parsed value will be silently overwritten.
As of Kafka 0.11.0. Because of the potential for message format conversion on the broker, the checksum returned by the broker may not match what was computed by the producer. It is therefore unsafe to depend on this checksum for end-to-end delivery guarantees. Additionally, message format v2 does not include a record-level checksum (for performance, the record checksum was replaced with a batch checksum). To maintain compatibility, a partial checksum computed from the record timestamp, serialized key size, and serialized value size is returned instead, but this should not be depended on for end-to-end reliability.
REDIS does not support null as a parameter, only as response. This was a deviation from the official protocol which should be avoided. Other clients explicitly do not allow this. Adds a null encoded string. Redis does not allow storing the null value by itself. This method will encode any null value as the four character long string "null". As a recommendation, this method should not be used directly unless this is the intented behavior. It is present to handle special cases such as encoding of JsonObject and JsonArray which may contain null values.