[
https://issues.apache.org/jira/browse/AVRO-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726222#action_12726222
]
Doug Cutting commented on AVRO-66:
----------------------------------
I didn't see your patch when I submitted mine. You missed the error case in
the Python responder. I inlined the schema, rather than reading it from a
file. It seems simple enough that it's not worth reading from a file. What do
you think?
> add RPC per-call metadata and a plugin API to access it
> -------------------------------------------------------
>
> Key: AVRO-66
> URL: https://issues.apache.org/jira/browse/AVRO-66
> Project: Avro
> Issue Type: New Feature
> Components: c, c++, java, python, spec
> Reporter: George Porter
> Attachments: AVRO-66.1.patch, AVRO-66.2.patch, AVRO-66.patch,
> AVRO-66.patch, AVRO-66.patch, AVRO-66.patch, AVRO-66.patch, AVRO-66.patch
>
>
> The RPC specification should support per-call metadata maps. Requestor and
> Responder should have methods that access this per-call metadata.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
