[
https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831177#action_12831177
]
Todd Lipcon commented on AVRO-341:
----------------------------------
I agree that the "payload" should not itself be avro-encapsulated. Instead, I
think the stream would look something like:
client:
SendCommandRecord for call Foo, callid 1
CommandData for callid 1, length 234 bytes
<param 1>
<param 2>
<param 3>
server:
SendResponseRecord for callid 1
ResponseData for callid 1, length 12 bytes
<frame 1 of response>
ResponseData for callid 2, length 24 bytes
<frame 2 of response>
(this is obviously not fleshed out - just trying to describe how I think
interleaving of avro "control" records could be done with the user-protocol
"payload" records.)
> 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.
