Github user apocolipse commented on the issue:
https://github.com/apache/thrift/pull/1084
@fumoboy007 There is `TAsyncClient` in TClient.swift as well as
`TAsyncTransport/Factory` in TTransport.swift, and the generator will generate
async clients properly (`--gen swift_3:async_clients`), for servers, the design
I've seen so far is that they're asynchronous by creating new transports for
each request for an async server, so its incumbent on the base thrift server
implementation to handle async code, in which the simple socket server I've
included should handle it fine, as well as the Perfect server example I posted
in the readme should work as well.
Can you elaborate on anything more that you'd like to see?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
