[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100422#comment-13100422
]
Doug Cutting commented on HADOOP-7557:
--------------------------------------
Extensibility in internet protocols (SMTP, DNS, LDAP, HTTP, SASL Digest, etc.)
is usually provided through lists of key/value pairs. All implementations do
not require any particular library. Protocol specifications are kept more
independent.
It would be good if our protocol metadata is easily interconvertable with other
network protocols, e.g., if Hadoop RPC metadata can be easily copied into HTTP
headers and/or Avro RPC metadata and vice versa.
So I would advocate that extensibility be provided through the well-known
protocol extensibility mechanism of a list of key/value pairs.
Do we have a case where this is inadequate?
> Make IPC and RPC headers be extensible
> ---------------------------------------
>
> Key: HADOOP-7557
> URL: https://issues.apache.org/jira/browse/HADOOP-7557
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
