You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2013/10/07 21:11:42 UTC

[jira] [Comment Edited] (THRIFT-2034) Give developers' C++ code direct access to socket FDs on server side

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

Jens Geyer edited comment on THRIFT-2034 at 10/7/13 7:09 PM:
-------------------------------------------------------------

Could that be made to fit into the processor events concept somehow?


was (Author: jensg):
Does C++ implement processor events?

> Give developers' C++ code direct access to socket FDs on server side
> --------------------------------------------------------------------
>
>                 Key: THRIFT-2034
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2034
>             Project: Thrift
>          Issue Type: Improvement
>          Components: C++ - Library
>    Affects Versions: 0.9
>            Reporter: Ben Craig
>            Assignee: Ben Craig
>             Fix For: 1.0
>
>         Attachments: socket_callbacks2.patch
>
>
> Occasionally, developers need to set some socket option that the Thrift maintainers haven't made a getter / setter for yet.  Sometimes the lack of a getter / setter is just because we haven't gotten to it, and sometimes it's because we don't want to provide (perhaps because of portability concerns).
> On the client side, developers can just call getSocketFD() and call getsockopt all day long.  On the server side, there is no such option.  In addition, it makes sense to allow separate access to the "listening" socket versus the "accepted" socket.



--
This message was sent by Atlassian JIRA
(v6.1#6144)