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/05/01 00:04:54 UTC

[jira] Updated: (AVRO-285) request-only messages

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

Doug Cutting updated AVRO-285:
------------------------------

    Attachment: AVRO-285.patch

Here's a version that is compatible.  In particular,
 - one-way messages specify a response type of "null" so they're parseable by older impls.  (the java parser is lenient in that it does not require this, but the java printer will always include this response type.)
 - "stateless" transports like HTTP always return a response for one-way messages

The socket transport is now "stateful", meaning:
  - requests and responses are only prefixed with handshakes until a successful handshake response is returned
  - once a successful handshake response has been returned, a one-way message has no response data

More tests have been added.  Still need to add a documentation to the spec.

I also fixed the RPC unit tests to no longer create a new client and server for each request but rather to reuse them.


> request-only messages
> ---------------------
>
>                 Key: AVRO-285
>                 URL: https://issues.apache.org/jira/browse/AVRO-285
>             Project: Avro
>          Issue Type: New Feature
>          Components: spec
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>         Attachments: AVRO-285.patch, AVRO-285.patch
>
>
> It might be useful to have a standard mechanism in Avro for transmitting messages that receive no response, not even an acknowledgement.

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