thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Geyer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (THRIFT-4672) IAsyncResult style methods not being supported by certain transports leads to issues in mixed ISync/IAsync use cases
Date Sat, 24 Nov 2018 20:51:00 GMT

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

Jens Geyer resolved THRIFT-4672.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Committed.

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

Mime
View raw message