[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126755#comment-13126755
]
Doug Cutting commented on HADOOP-7557:
--------------------------------------
> I added the protocolKind to distinguish between these.
This seems analagous to HTTP's Content-Type and may be useful if we expect to
support multiple kinds of RPC payloads from a server. Do we expect that
long-term? If we do only short-term we might handle different kinds of
payloads with the ConnectionHeader version.
Also, why are ConnectionHeader and IpcConnectionHeader separate? It makes
sense to separate them if IpcConnectionHeader is specific to the protocolKind,
but otherwise, if both headers are universal, perhaps they could be combined.
If they're universal then they shouldn't depend on Writable, Protocol Buffers
or Avro, but rather should be explicitly and fully specified in the protocol.
> Make IPC header be extensible
> -------------------------------
>
> Key: HADOOP-7557
> URL: https://issues.apache.org/jira/browse/HADOOP-7557
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Attachments: HADOOP-7557.patch, IpcHeader.proto, ipcHeader1.patch,
> ipcHeader2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
