[ 
https://issues.apache.org/jira/browse/AVRO-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Zeyliger updated AVRO-267:
---------------------------------

    Attachment: AVRO-267.patch.txt

Attaching a patch that implements rpcsend and rpcreceive.

One questionable thing I'll point out is that I extended JsonDecoder to take a 
String (in addition to an InputStream).  Since command-line arguments end up as 
strings, I wanted to avoid converting a string to a byte array in order to make 
an InputStream.  Jackson has lots of constructors, Reader and String amongst 
them.  What do you think?

I thought about the server accepting many RPCs (not just one), but I decided 
against it.  Partially because of netcat's model, and partially because the 
server has to return something, and "null" isn't always an option (since it may 
not be in the schema).  Returning an exception is always possible, but since 
these are essentially tools for facilitating testing of servers I went for one 
message.

Finally, applying this patch depends very slightly (Main and Util classes) on 
AVRO-245.

-- Philip

> Tool (for "avroj") to send and receive a single RPC from the commandline
> ------------------------------------------------------------------------
>
>                 Key: AVRO-267
>                 URL: https://issues.apache.org/jira/browse/AVRO-267
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>         Attachments: AVRO-267.patch.txt
>
>
> Vaguely similar to "netcat" and "netcat -l", "avroj rpcreceive" and "avroj 
> rpcsend" would send receive or send a single RPC (using the HTTP transport).  
> The former is required to have a response pre-determined and echoes the 
> request; the latter echoes any response it receives.

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

Reply via email to