[
https://issues.apache.org/jira/browse/AVRO-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-340:
------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this.
> I wouldn't mind the spec suggesting that the url is
> http://example.host:port/avro, though other URLs are acceptable.
I think there might be cases where, for security or otherwise, one might wish
to use different urls for different protocols. If you feel this would be
useful, can you file another issue?
> Do we need to explicitly mention that it is acceptable to use the same socket
> for multiple HTTP requests (keep-alive, I believe, in HTTP terms)?
I think that's covered in the HTTP spec. We don't mention connections,
proxies, redirects or any of that stuff. If folks are confused, then we might
add clarifications as needed.
> 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
>
> Attachments: AVRO-340.patch
>
>
> 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.
