You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2009/07/09 01:19:14 UTC

[jira] Commented: (AVRO-76) Add plug-in mechanism for manipulating per-call metadata

    [ https://issues.apache.org/jira/browse/AVRO-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728959#action_12728959 ] 

Doug Cutting commented on AVRO-76:
----------------------------------

Some quick comments:
 - Requestor and Responder should each support a list of plugins, not just a single plugin, so that one might implement authentication, authorization, tracing and other orthogonal mechanisms each as a plugin.
 - Plugins should be added with an addPlugin() method, not through constructors.  Over time, adding optional parameters leads to confusing parameter lists.  In the case of getClient(), we might change the signature to accept a Requestor
 - Metadata map should be passed as a parameter to the plugin's methods.



> Add plug-in mechanism for manipulating per-call metadata
> --------------------------------------------------------
>
>                 Key: AVRO-76
>                 URL: https://issues.apache.org/jira/browse/AVRO-76
>             Project: Avro
>          Issue Type: Sub-task
>            Reporter: George Porter
>            Assignee: George Porter
>         Attachments: AVRO-76.patch
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.