[
https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831209#action_12831209
]
Todd Lipcon commented on AVRO-341:
----------------------------------
bq. It terms of vocabulary, I feel that discovery is more about finding all
machines running Avro services (like bonjour or Zeroconf). The term
introspection seems more appropriate here.
+1. Thrift calls this idea "reflection" though they failed to implement it in a
useful manner so I think it actually got pulled out.
bq. create a base RPC proxy for clients that passes the response bytes "up" to
a higher level response processor
This will be tricky to integrate with streaming RPC, and I think will make
coding somewhat difficult, since in effect we'd have to embed one avro decoder
inside another. I think it'll simplify things to look at the avro session as a
state machine that flip flops between "control plane" messages and "user data
plane" messages. The user data planed messages are of course in themselves
avro-encoded, but using the user's protocol and types, rather than one we've
defined. The control plane messages provide a sort of framing that connects the
user frames to particular calls. Does that make sense?
> 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.
