[
https://issues.apache.org/jira/browse/THRIFT-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693994#comment-13693994
]
James E. King, III commented on THRIFT-1939:
--------------------------------------------
Part of what you are looking for may have been solved in my changes on JIRA-66
which were never brought into the core product. They were done against version
0.5.0 and I re-wrote much of the transport part of the C# library so that you
could have two-way communication, multiple services on a connection (this
feature is called Channels), secure connections with optional certificate
checking, and multiple outstanding requests. I don't believe asynchronous
notification was part of the deal but I expect it would be trivial to add. All
of this worked with .NET 2.0. Sadly the changes are quite out of date.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
