avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-285) request-only messages
Date Fri, 30 Apr 2010 00:26:54 GMT

    [ https://issues.apache.org/jira/browse/AVRO-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862491#action_12862491

Doug Cutting commented on AVRO-285:

> Isn't this a backwards incompatible change?

Good point.

So maybe the change should be that, when:
 - the message response type is null
 - no message errors are specified
 - the previously-non-standard socket transport is used
 - a connection has been established with a handshake, and
 - "one-way": true is specified (which existing implementations should ignore)
then no response data is written at all.

In other words, one-way only has a special meaning for stateful transports, and previously
the spec defined no stateful transports.  For "stateless" transports like HTTP, one-way is

> 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
> 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.

View raw message