You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "David Reiss (JIRA)" <ji...@apache.org> on 2008/05/09 00:08:55 UTC
[jira] Created: (THRIFT-1) Fully-asychronous client and server
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.
[jira] Commented: (THRIFT-1) Fully-asychronous client and server
Posted by "Alexander Shigin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658964#action_12658964 ]
Alexander Shigin commented on THRIFT-1:
---------------------------------------
I've got async client for python with asyncore. And I'm trying to make C++ nonblocking server a full async.
> 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.
[jira] Commented: (THRIFT-1) Fully-asychronous client and server
Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658939#action_12658939 ]
Bryan Duxbury commented on THRIFT-1:
------------------------------------
We've already got an asynchronous server for Java. I'd be interested to think about async clients, though.
> 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.
[jira] Commented: (THRIFT-1) Fully-asychronous client and server
Posted by "Esteve Fernandez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658989#action_12658989 ]
Esteve Fernandez commented on THRIFT-1:
---------------------------------------
David: I think it would be better if this ticket depended on several subtasks, one for each language. What do you think?
> 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.
[jira] Commented: (THRIFT-1) Fully-asychronous client and server
Posted by "Esteve Fernandez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658946#action_12658946 ]
Esteve Fernandez commented on THRIFT-1:
---------------------------------------
Bryan: are you using a specific library (a la Apache MINA) or is it just pure NIO + Listeners? I worked on the client part using MINA, returning a DefaultReadFuture (http://mina.apache.org/report/trunk/apidocs/org/apache/mina/common/DefaultReadFuture.html) on every call.
It's basically the same approach as THRIFT-148: don't return the actual value, but a future/deferred/promise and attach callbacks/listeners that will be fired when the return value becomes available.
> 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.