avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Massie (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-341) specify avro transport in spec
Date Tue, 09 Feb 2010 01:53:28 GMT

    [ https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831249#action_12831249

Matt Massie commented on AVRO-341:

Todd> look at the avro session as a state machine that flip flops between "control plane"
messages and "user data plane" messages

Sounds good to me.  The service number rules at the end of my message sort of speaks to that
separation.  We need to tease out the details to do it better.

Doug> 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.

If the team agrees on different terminology, I will happily do the search/replace.  Being
consistent is important I agree, but it would be ideal to be consistent with the wider community
outside of Avro.  

Doug> Except the Wikipedia page says that HTTP is at the application level

http://en.wikipedia.org/wiki/OSI_model .   RPC is listed as a Layer 5 (Session) example. 
 HTTP is correctly at the Application level but this Jira is about RPC and not HTTP.

> 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.

View raw message