[
https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831174#action_12831174
]
Doug Cutting commented on AVRO-341:
-----------------------------------
> First off, we should probably call this a "protocol".
It's fair to use a term differently in different contexts. Avro is not using
terms in accord with the OSI model. Avro's spec does try to define each term
when its first used, and to use terms consistently within that document. Can't
we use the same terminology here? If we'd like to switch terminology, then we
should also update the spec and the implementations, no?
> I'd like us to consider describing Avro's protocol in terms of (and here the
> terminology falls down) an Avro protocol, or at least in terms of Avro
> records.
I think this could be deceptive if we don't support Avro versioning features
here. I think it's often simpler to bootstrap a system not using itself but
using a more primitive system. We'd like the transport to be extensible. Many
protocols use a combination of named commands, key/value meta-data and a binary
payload to provide extensibility. A description at this level in Avro is
possible, but would probably not be able to describe the internal structure of
every command's payload. So, in practice, folks might not in fact implement a
so-specified transport using Avro, as that might require an extra copy of
payload data. So we might stick to using Avro to describe just the
command+metadata part, and leave payloads outside of this. Or we might
alternately describe the command+metadata part as something as simple as
<command>(<newline><name><colon><value><newline>)*<newline><payload>.
> specify avro transport in spec
> ------------------------------
>
> Key: AVRO-341
> URL: https://issues.apache.org/jira/browse/AVRO-341
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Doug Cutting
>
> We should develop a high-performance, secure, transport for Avro. This
> should be named with avro: uris.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
