[jira] [Commented] (THRIFT-3550) Latest indexed version of the perl lib on CPAN is 0.8.0, although 0.9.0 is present
[ https://issues.apache.org/jira/browse/THRIFT-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606994#comment-15606994 ] James E. King, III commented on THRIFT-3550: Here's the normal "getting started" for CPAN: http://www.cpan.org/misc/cpan-faq.html#How_contribute_modules I've done a fair amount of work with the perl modules recently. If I can help please let me know. > Latest indexed version of the perl lib on CPAN is 0.8.0, although 0.9.0 is > present > -- > > Key: THRIFT-3550 > URL: https://issues.apache.org/jira/browse/THRIFT-3550 > Project: Thrift > Issue Type: Wish > Components: Perl - Library >Affects Versions: 0.9.3 >Reporter: David Morel > > Running cpanm or cpan installs version 0.8.0 of the perl lib, although 0.9.0 > has been uploaded on PAUSE. > Also, would be nice to have v 0.9.3 since it's available? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] thrift issue #1084: THRIFT-3773 Swift 3 Native Library
Github user apocolipse commented on the issue: https://github.com/apache/thrift/pull/1084 @fumoboy007 so for clients you should be doing something like this: ```swift let factory = THTTPSessionTransport.Factory(url: serviceURL) let client = HermesAsyncClient(with: TBinaryProtocol.self, factory: factory) ``` For servers, its all about the server, no need to have an async processor I'll need to update the Perfect HTTP Server example I have on my github for HTTP servers, but basically the setup is something like this (same as TSocketServer: ```swift let server = try? TSocketServer(port: 9090, service: MyConcreteService(), // your implementation of thrift service inProtocol: TBinaryProtocol.self, outProtocol: TBinaryProtocol.self, processor: MyServiceProcessor.self) // generated service processor ``` Since it leverages generics, each request creates its own processor rather than re-using the same one over and over (If you look at the TSocketServer impl, you'll see something like ```swift let processor = Processor(service: self.serviceHandler) processor.process(on: inproto, outProtocol: outproto) ```) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (THRIFT-3952) Upgrade from v1.5.8 to current version for slf4j
[ https://issues.apache.org/jira/browse/THRIFT-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Gould updated THRIFT-3952: --- Affects Version/s: 0.10.0 Priority: Minor (was: Major) > Upgrade from v1.5.8 to current version for slf4j > > > Key: THRIFT-3952 > URL: https://issues.apache.org/jira/browse/THRIFT-3952 > Project: Thrift > Issue Type: Dependency upgrade >Affects Versions: 0.9.3, 0.10.0 >Reporter: Tim Webex >Priority: Minor > > Are slf4j-api-1.5.8.jar and slf4j-log4j12-1.5.8.jar intended to support the > older versions of Java? These are pretty old versions of slf4j. > Can they be upgraded to the current version? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
