You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Craig Peterson (JIRA)" <ji...@apache.org> on 2014/01/15 23:28:19 UTC

[jira] [Commented] (THRIFT-1939) C#: Real async support

    [ https://issues.apache.org/jira/browse/THRIFT-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872699#comment-13872699 ] 

Craig Peterson commented on THRIFT-1939:
----------------------------------------

I've started trying to implement a true async version as well, and it does seem particularly difficult to avoid breaking changes. Not impossible, but at a minimum the framework version would need to be increased to 4.5, which could cause problems for people dependent on older framework versions.

I do believe there are performance improvements to be made for both client and server, so it is worthwhile, but definitely a heavy undertaking.

> C#: Real async support
> ----------------------
>
>                 Key: THRIFT-1939
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1939
>             Project: Thrift
>          Issue Type: New Feature
>          Components: C# - Compiler, C# - Library
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>
> This process would affect both the compiler and the library. The compiler needs to generate real async-await functions, and the library needs to be changed to use the async methods on Socket.
> If this was the default C# library, then the language version required would jump to C# 5, the .NET runtime required would be 4.5, and Mono support would become "beta". I think a better way would be to release a second .NET 4.5 library, with a new language parameter "csharp:5", or a new language "csharp5". I'm more in favor of the former, but it may make the compiler a little hairier to write.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)