Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@thrift.apache.org
Date: Wed, 14 Nov 2012 21:38:12 +0000 (UTC)
From: "Ben Craig (JIRA)" <jira@apache.org>
To: dev@thrift.apache.org
Message-ID: <1490147926.116023.1352929092878.JavaMail.jiratomcat@arcas>
In-Reply-To: <1171569390.57901.1347287047572.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (THRIFT-1690) Sockets and Pipe Handles truncated
 on Win64
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ben Craig commented on THRIFT-1690:
-----------------------------------

So what is the expectation of source compatibility with Thrift?  If I change TSocket and TServerSocket to be TCP only, TPipe and TServerPipe to be localhost named transports, and create TAnonymousPipe classes, would the code breaks be met with insurmountable resistance?
                
> Sockets and Pipe Handles truncated on Win64
> -------------------------------------------
>
>                 Key: THRIFT-1690
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1690
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.9
>         Environment: 64-bit Windows
>            Reporter: Ben Craig
>            Assignee: Roger Meier
>         Attachments: lib_socket_typedef.patch, libthrift_pipe_size.patch, libthrift_warning_purge.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> On 64-bit Windows, "int" is a 32-bit value.  SOCKET and HANDLE are 64-bit.
> All of the files dealing with sockets in thrift use "int" as the type of a socket, as this is the idiomatic way to handle sockets on POSIX systems.  For portability, a SOCKET typedef is probably needed.
> For the Pipe Server and Pipe Transport, HANDLEs are cast to ints to store as member variables for some reason (maybe to avoid #including <windows.h> in a header?).
> Both of these situations can result in invalid handles being used (and valid handles being leaked) when the system is under load.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira