You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King III (JIRA)" <ji...@apache.org> on 2018/12/27 15:25:16 UTC

[jira] [Closed] (THRIFT-4672) IAsyncResult style methods not being supported by certain transports leads to issues in mixed ISync/IAsync use cases

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

James E. King III closed THRIFT-4672.
-------------------------------------

> IAsyncResult style methods not being supported by certain transports leads to issues in mixed ISync/IAsync use cases
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-4672
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4672
>             Project: Thrift
>          Issue Type: Bug
>          Components: C# - Compiler
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>            Priority: Major
>              Labels: async
>             Fix For: 0.12.0
>
>
> The {{csharp:async}} switch causes the compiler to change the implementation of the client side call stubs to always use IAsyncResult. This causes issues, because the IAsyncResult call style is not supported by all transports.
> If such a transport is used, the code finally calls the {{TTransport}} implementations of {{BeginFlush}} and {{EndFlush}} - either one of these simply throws an exception, causing the outgoing call to fail.
> What is highly unexpected here is the fact, that due to the {{send_Xxx}} method implementation change also {{ISync}} interface is affected as soon as {{csharp:async}} is used.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)