[
https://issues.apache.org/jira/browse/THRIFT-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090431#comment-15090431
]
ASF GitHub Bot commented on THRIFT-3510:
----------------------------------------
Github user nsuke commented on the pull request:
https://github.com/apache/thrift/pull/762#issuecomment-170200180
> This doesn't really make sense on the server side since if you implement
a service you end up leaving all the async method unimplemented.
You can implement both by using Interface.Method syntax for at least one of
the two.
Generating XxxAsync as your patch does feels more straightforward and
natural, though.
> Add HttpTaskAsyncHandler implementation
> ---------------------------------------
>
> Key: THRIFT-3510
> URL: https://issues.apache.org/jira/browse/THRIFT-3510
> Project: Thrift
> Issue Type: New Feature
> Components: C# - Compiler, C# - Library
> Reporter: Adam Connelly
> Priority: Minor
>
> The THttpHandler doesn't support an async pipeline. This means that it's
> difficult for service implementations to make async calls. If there was an
> implementation of HttpTaskAsyncHandler, you could write services using async
> calls.
> Additionally, if you generate the C# classes with the current async support,
> you get a single interface with both sync and async methods. This doesn't
> really make sense on the server side since if you implement a service you end
> up leaving all the async method unimplemented. It would be useful if there
> were separate sync and async interfaces to make this a bit tidier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
