[
https://issues.apache.org/jira/browse/AVRO-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-341:
------------------------------
Attachment: aep-001.txt
Perhaps we should adopt a PEP-like process for things like this.
http://www.python.org/dev/peps/pep-0001/
In that vein, I've attached the beginnings of an Avro Enhancement Proposal
(AEP) for this feature.
Bruce, would you like to help flesh this out? I think we should first come to
general agreement about a specification, then implement it in at least two
languages, perhaps changing the design as we go, before we declare it as a
stable Avro feature.
Does that sound like a reasonable process?
> 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
> Attachments: aep-001.txt
>
>
> 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.
