[ https://issues.apache.org/jira/browse/THRIFT-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091069#comment-15091069 ]
ASF GitHub Bot commented on THRIFT-3510: ---------------------------------------- Github user adamconnelly commented on the pull request: https://github.com/apache/thrift/pull/762#issuecomment-170354621 Yeah, I already changed my settings to spaces for indentation, and two spaces for indents, which seemed to be what the existing code was using. It's just that there's a load of other things (like newlines before else statements for example), and for some reason VS seemed to reformat the entire file. Anyhow, I reverted all those whitespace changes, so it shouldn't be an issue. > 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)