Sorry. I wasn't paying attention. Feel free to reopen it, or I will when I get online. Sent from my BlackBerry.
----- Original Message ----- From: Bryan Duxbury <[EMAIL PROTECTED]> To: [email protected] <[email protected]> Sent: Tue May 27 10:12:00 2008 Subject: Re: [jira] Closed: (THRIFT-23) TUnixSocket This one was for the java libraries. I created two tickets because it seemed extremely likely they would get done separately. Would we rather have one issue, a parent issue with subissues for each library, or separate issues? -Bryan On May 27, 2008, at 9:58 AM, David Reiss (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/THRIFT-23? > page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > David Reiss closed THRIFT-23. > ----------------------------- > > Resolution: Duplicate > Assignee: David Reiss > > Duplicate of THRIFT-22. > >> TUnixSocket >> ----------- >> >> Key: THRIFT-23 >> URL: https://issues.apache.org/jira/browse/THRIFT-23 >> Project: Thrift >> Issue Type: New Feature >> Components: Library (Java) >> Reporter: Bryan Duxbury >> Assignee: David Reiss >> Priority: Minor >> >> At Rapleaf, we'd love to have a TUnixSocket and TUnixServerSocket >> that ran in Java. Before someone chimes in and says, "Java doesn't >> support Unix sockets!", I would point to JRuby's RubyUnixSocket/ >> Server classes. They use JNA to get down to the bare metal and >> make it work. If we could take advantage of that class, then we'd >> have a really fast local machine transport. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >
