[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126195#comment-13126195
]
Sanjay Radia commented on HADOOP-7557:
--------------------------------------
> This is not a user extension point....
> ... like security that's used by all message encodings, why not use an
> encoding-independent format in the header? ...
Essentially you are arguing that IpcHeader does not need to be extensible and
that *essentially* we should merge the "hrpc" header and the ipcHeader. I do
believe it is missing the "protocolKind" field since there are 3 existing
protocols (3 rpc engines) at the next layer. Hence if the header *had* been
extensible in the past we would have been able to add the field easily in a
backward compatible fashion.
> 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
