[
https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831216#action_12831216
]
Doug Cutting commented on AVRO-341:
-----------------------------------
Matt> look at the avro session as a state machine that flip flops between
"control plane" messages and "user data plane" messages
Except the Wikipedia page says that HTTP is at the application level, not at
the session level. Seriously, we just need to pick some terms, define them,
and use them consistently. Protocol and Transport both currently have clear,
unambiguous definitions in Avro. Alignment with OSI terminology is not a
priority for me. If it is for you, then please propose a patch updating the
spec and all of the implementations.
Todd> look at the avro session as a state machine that flip flops between
"control plane" messages and "user data plane" messages
+1 this makes good sense to me.
> 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.
