[
https://issues.apache.org/jira/browse/AVRO-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860060#action_12860060
]
Doug Cutting commented on AVRO-285:
-----------------------------------
I've started looking into implementing this. We still need a handshake to take
place, so that client and server versions need not match exactly. But, without
a response, there's no way to make a piggybacked handshake. So, I think, to
implement this, we need to factor the handshake logic out of every request and
response.
This can be done compatibly. HTTP always sends a response, so with that
transport there will always be a handshake response, and that's the only
transport specified today.
For the Java implementation of this I thus intend to refactor handshaking.
I'll use a non-standard transport to test unidirectional messages, like
SocketTransciever and SocketServer.
> 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
>
> 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.
