thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Ballard (JIRA)" <j...@apache.org>
Subject [jira] Commented: (THRIFT-74) Thrift::Socket.new should accept optional timeout argument
Date Fri, 11 Jul 2008 01:55:31 GMT

    [ https://issues.apache.org/jira/browse/THRIFT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612725#action_12612725
] 

Kevin Ballard commented on THRIFT-74:
-------------------------------------

It does indeed expose timeout as an instance variable with an accessor, so you can set it
or change it after the Socket has been created.

I believe connect already times out, natively. I'm not aware of any way to control this timeout,
though. I can implement timeout for write, but unfortunately this will break jruby compatibility
(jruby doesn't implement the IO#foo_nonblock methods properly).

> Thrift::Socket.new should accept optional timeout argument
> ----------------------------------------------------------
>
>                 Key: THRIFT-74
>                 URL: https://issues.apache.org/jira/browse/THRIFT-74
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Library (Ruby)
>            Reporter: Kevin Ballard
>            Priority: Minor
>         Attachments: 0001-rb-Add-optional-timeout-argument-to-Thrift-Socket.patch, 0001-rb-Add-optional-timeout-argument-to-Thrift-Socket.patch
>
>
> Thrift::Socket.new should accept an optional timeout argument which will raise an TransportException
if no data was returned during a #read in that time period.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message