Uploaded image for project: 'Apache Avro'
  1. Apache Avro
  2. AVRO-1662

Protocol Handshake vs Message Framing

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.7.7
    • Fix Version/s: None
    • Component/s: java, spec
    • Labels:
      None

      Description

      The 1.7.7 specification explains the structure of framing but is ambiguous as to whether and how this applies to the handshake.

      As the handshake request and responses are Avro values, they don't require framing per-se.

      However, testing with the Java SaslSocketTransceiver has shown that, after SASL completion, a 4-byte header is sent by the client, which isn't specified in the handshake section of the specification, and the following n bytes includes the subsequent protocol-specific call.

      If the handshake requests and responses are legitimately framed messages, then it seems there should be a terminating frame of 0 bytes between the handshake request and subsequent protocol request.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              inbuninbu Jeff Douglas
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: