[
https://issues.apache.org/jira/browse/THRIFT-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689261#action_12689261
]
David Reiss commented on THRIFT-388:
------------------------------------
Almost. It also makes the C++ and Erlang servers recognize the new enum as an
alias for T_CALL.
Once this change is "widely deployed", we can make clients send a different
message type code if they are making a oneway call.
Once that change is widely deployed, it will be easy to produce a generic proxy
that properly distinguishes between oneway and non-oneway calls. This is my
goal.
But it will also be possible to have the server decide whether or not to
respond based on the call type, which would make it possible to convert a
oneway call to a non-oneway call without causing synchronization problems, or
even decide at run time that a call should be oneway.
> Use a separate wire format for async calls
> ------------------------------------------
>
> Key: THRIFT-388
> URL: https://issues.apache.org/jira/browse/THRIFT-388
> Project: Thrift
> Issue Type: Improvement
> Reporter: David Reiss
> Assignee: David Reiss
> Priority: Minor
> Attachments:
> 0001-THRIFT-388.-Create-a-ONEWAY-message-type-that-is-a.patch
>
>
> If async calls look different from normal calls on the wire, then a proxy
> with no access to the particular IDL will be able to distinguish them. That
> will be good.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
