[
https://issues.apache.org/jira/browse/THRIFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971763#action_12971763
]
David Jeske edited comment on THRIFT-1 at 12/15/10 2:49 PM:
------------------------------------------------------------
To clarify, it looks like Thrift has a non-blocking I/O implementation in most
stub-languages, but the only language that supports an async handler interface
for client or server is Python-Twisted. (an async handler interface requires
return values provided via callback, so the handler can let go of the
request-thread without producing a result)
Eric Bernhardsson did some work on a C++ async handler interface which hasn't
been incorporated yet.
http://markmail.org/thread/7xl2fpwn3hvao2jh#query:+page:1+mid:7xl2fpwn3hvao2jh+state:results
One route for Java-async-handlers is to build on Netty, a twisted-like
event-driven framework for Java. Another route is to avoid dependencies on a
framework and refactor the java-core to handle async return results and add the
ability for the stubs to generate 'return result callbacks' that decouple the
handler-thread from the return result.
was (Author: jeske):
To clarify, it looks like Thrift has a non-blocking I/O implementations in
most languages, but the only language that supports an async handler interface
for client or server is Python-Twisted. (an async handler interface requires
return values provided via callback, so the handler can let go of the
request-thread without producing a result)
Eric Bernhardsson did some work on a C++ async handler interface which hasn't
been incorporated yet.
http://markmail.org/thread/7xl2fpwn3hvao2jh#query:+page:1+mid:7xl2fpwn3hvao2jh+state:results
One route for Java-async-handlers is to build on Netty, a twisted-like
event-driven framework for Java. Another route is to avoid dependencies on a
framework and refactor the java-core to handle async return results and add the
ability for the stubs to generate 'return result callbacks' that decouple the
handler-thread from the return result.
> Fully-asychronous client and server
> -----------------------------------
>
> Key: THRIFT-1
> URL: https://issues.apache.org/jira/browse/THRIFT-1
> Project: Thrift
> Issue Type: New Feature
> Environment: All
> Reporter: David Reiss
>
> All Thrift servers currently require a thread to be tied up for every
> outstanding request being serviced.
> In addition, all clients have the same requirement, but workarounds are
> easier.
> This is also the first JIRA issue in the Thrift project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
