[
https://issues.apache.org/jira/browse/AVRO-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847633#action_12847633
]
Xing Jin commented on AVRO-484:
-------------------------------
Hello Jeff,
Just attached the patch a moment ago. Scott also suggested to have the RPC
interop test to make sure it works. Right now, it is probably not fully there
yet. We (mostly Scott) will figure out what to happen next. I will always be
available for questions or issues with this patch at this email address. Thanks!
Xing
--- On Fri, 3/19/10, Jeff Hammerbacher (JIRA) <j...@apache.org> wrote:
From: Jeff Hammerbacher (JIRA) <j...@apache.org>
Subject: [jira] Commented: (AVRO-484) avro C++ HTTP rpc support
To: xji...@yahoo.com
Date: Friday, March 19, 2010, 1:48 PM
[
https://issues.apache.org/jira/browse/AVRO-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847572#action_12847572
]
Jeff Hammerbacher commented on AVRO-484:
----------------------------------------
Hey Xing,
Thanks for the contribution!
http://hadoop.apache.org/avro/docs/current/spec.html#HTTP+as+Transport has the
details on how to use HTTP for Avro RPC. Also, I don't see a patch attached,
but you can implement the RPC interop tests to ensure you've got things working
correctly. Currently only Java and Python have working RPC implementations.
Thanks,
Jeff
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
> avro C++ HTTP rpc support
> -------------------------
>
> Key: AVRO-484
> URL: https://issues.apache.org/jira/browse/AVRO-484
> Project: Avro
> Issue Type: Improvement
> Components: c++
> Reporter: Xing Jin
> Attachments: http.v2.patch
>
>
> Upon Scott Banachowski's request, this is to add HTTP transport support for
> the rpc usage of avro C++ version. The current implementation uses HTTP POST
> to send over a request body (of any content) and the server side responds
> with a standard HTTP response body (of any content).
> Current status: it only requires a user to provide a streambuf input and
> define a function that contains the business logic to generate the serialized
> content into a response streambuf. testhttpserver would be a good example
> there.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
