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 2010/01/15 21:28:56 UTC

[jira] Commented: (AVRO-340) specify http transport in spec

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

Doug Cutting commented on AVRO-340:
-----------------------------------

The spec should also describe how URIs may be used to name Avro transports.  Initially we'll only specify http: uris.

Avro should only specify transports that we intend to support long-term.  We may add other transports subsequently, but, in the meantime, we should not encourage implementations of non-standard transports, as they will complicate compatibility: we do not want to have to support them long-term.

Each Avro implementation should implement clients for all transports in the spec, so that applications can talk to any Avro-based service.  They need not implement servers for all server transports however.


> specify http transport in spec
> ------------------------------
>
>                 Key: AVRO-340
>                 URL: https://issues.apache.org/jira/browse/AVRO-340
>             Project: Avro
>          Issue Type: Improvement
>          Components: spec
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> The use of HTTP as an Avro RPC transport should be described in the Avro spec.

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